System and method for verifying verifiable claims

ABSTRACT

Methods, systems, and apparatus, including computer programs encoded on computer storage media, for claim verification. One of the methods includes: receiving, from a first entity, a request for verifying a verifiable claim (VC) that comprises a digital signature; obtaining, based on the VC, a public key associated with a second entity; determining that the digital signature is created based on a private key associated with the public key; and verifying the VC based on the determination.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation application of InternationalApplication No. PCT/CN2019/094427, filed with the State IntellectualProperty Office (SIPO) of the People's Republic of China on Jul. 2,2019. The entire content of the above-identified application isincorporated herein by reference.

TECHNICAL FIELD

This application generally relates to methods and devices for managingdecentralized identifiers and verifiable claims based on blockchaintechnology.

BACKGROUND

Traditional identity management systems are based on centralizedauthorities such as corporate directory services, certificateauthorities, or domain name registries. Each of the centralizedauthorities may serve as a root of trust that provides credibility tothe identity it endorses. For such systems, data associated with theidentities is often stored in centralized databases, if not traditionalinformation storage media. The maintenance of identity of each person orentity is under the control of the centralized authorities. Given itsnature, traditional identity management systems are subject to securityrisks suffered by each of the centralized authorities and provideinefficient mechanisms for the aggregation of identities or credentialsprovided by different centralized authorities. In such systems,individual entities or identity owners are often neither free to choosethe root of trust nor in control over their own identities orcredentials. Authentication and verification of their identities oftenprove to be inefficient.

Blockchain technology provides the opportunity to establish atrustworthy decentralized system that does not require trust in eachmember of the system. Blockchain provides data storage in adecentralized fashion by keeping the data in a series of data blockshaving precedence relationship between each other. The chain of blocksis maintained and updated by a network of blockchain nodes, which arealso responsible for validating data under a consensus scheme. Thestored data may include many data types, such as financial transactionsamong parties, historical access information, etc.

Many blockchains (e.g., the Ethereum blockchain) have enabled blockchaincontracts (also referred to as smart contracts) that are executedthrough blockchain transactions. Blockchain transactions are signedmessages originated by externally owned accounts (e.g., blockchainaccounts), transmitted by the blockchain network, and recorded in theblockchain. The blockchain contracts may be written to achieve variousfunctions, such as adding data to blockchain accounts, changing data inthe blockchain, etc. Thus, the blockchain can be maintained and updatedby executing various blockchain transactions.

Blockchain technology provides the means for managing a root of trustwithout centralized authority. Identity management systems built basedon blockchain often present substantive technical barriers for theregular user by requiring storage of a blockchain ledger, capabilitiesto create and execute blockchain transactions and contracts, orparticipation in the consensus scheme of the blockchain. An identityholder may be required to keep important identity credentials such ascryptographic keys, which may subject the identity holder to the risk ofloss of identity when such identity credentials are compromised.Furthermore, for business entities with the needs to manage identitiesfor a large number of users, such identity management systems oftenprove to be inefficient and user-unfriendly. Mapping between identitiesmanaged by such an identity management system and accounts or serviceIDs kept by business entities are often difficult to maintain. Finally,such identity management systems often require frequent access to andinteraction with the blockchain network, which may be costly andresource consuming.

SUMMARY

Various embodiments of the specification include, but are not limitedto, systems, methods, and non-transitory computer readable media forclaim verification.

According to some embodiments, a computer-implemented method for claimverification comprises receiving, from a first entity, a request forverifying a verifiable claim (VC) that comprises a digital signature,obtaining, based on the VC, a public key associated with a secondentity, determining that the digital signature is created based on aprivate key associated with the public key, and verifying the VC basedon the determination.

In some embodiments, the obtaining a public key associated with a secondentity comprises identifying the second entity based on an identifier inthe VC.

In some embodiments, the identifier is a decentralized identifier (DID);the obtaining a public key associated with a second entity comprisessending, to a blockchain node of a blockchain, a blockchain transactioncomprising information associated with the DID, wherein the blockchaintransaction is for retrieving a DID document corresponding to the DID,obtaining the DID document from the blockchain, and retrieving a publickey from the DID document. In some embodiments, the blockchaintransaction invokes a blockchain contract for managing relationshipsbetween DIDs and DID documents.

In some embodiments, the method further comprises obtaining a status ofthe VC and determining that the status of the VC is valid. In someembodiments, the obtaining a status of the VC comprises obtaining thestatus from a blockchain storing information associated with a pluralityof VCs.

In some embodiments, the determining that the status of the VC is validcomprises obtaining a first hash value associated with the VC along withthe status of the VC, determining a second hash value by applying a hashfunction on the VC, and authenticating the status of the VC by comparingthe first hash value with the second hash value.

In some embodiments, the obtaining a first hash value associated withthe VC along with the status of the VC comprises sending, to ablockchain node of the blockchain, a blockchain transaction forretrieving the first hash value and the status, the blockchaintransaction comprising the DID associated with the subject of the VC.

In some embodiments, the method further comprises receiving, from thefirst entity, an account identifier associated with a subject of the VC,obtaining a DID associated with the subject of the VC based on apre-stored mapping relationship between the account identifier and theDID, obtaining a DID document associated with the DID, obtaininginformation associated with a service endpoint for managing VCs from theDID document, and obtaining the VC from the service endpoint.

In some embodiments, the method further comprises sending a message tothe first entity confirming that the VC is verified.

In some embodiments, the verifying the VC comprises obtaining, from theVC, an issuance date of the VC and validating the obtained issuance datebased on a comparison between the obtained issuance date and a currentdate.

In some embodiments, the verifying the VC comprises obtaining, from theVC, an expiration date of the VC and validating that the VC has notexpired based on the expiration date and a current date.

According to other embodiments, a system for claim verificationcomprises one or more processors and one or more computer-readablememories coupled to the one or more processors and having instructionsstored thereon that are executable by the one or more processors toperform the method of any of the preceding embodiments.

According to yet other embodiments, a non-transitory computer-readablestorage medium is configured with instructions executable by one or moreprocessors to cause the one or more processors to perform the method ofany of the preceding embodiments.

According to still other embodiments, an apparatus for claimverification comprises a plurality of modules for performing the methodof any of the preceding embodiments.

According to some embodiments, a system for claim verification comprisesone or more processors and one or more computer-readable memoriescoupled to the one or more processors and having instructions storedthereon that are executable by the one or more processors to performoperations comprising receiving, from a first entity, a request forverifying a verifiable claim (VC) that comprises a digital signature,obtaining, based on the VC, a public key associated with a secondentity, determining that the digital signature is created based on aprivate key associated with the public key, and verifying the VC basedon the determination.

According to other embodiments, a non-transitory computer-readablestorage medium is configured with instructions executable by one or moreprocessors to cause the one or more processors to perform operationscomprising receiving, from a first entity, a request for verifying averifiable claim (VC) that comprises a digital signature, obtaining,based on the VC, a public key associated with a second entity,determining that the digital signature is created based on a private keyassociated with the public key, and verifying the VC based on thedetermination.

According to yet other embodiments, an apparatus for claim verificationcomprises a receiving module for receiving, from a first entity, arequest for verifying a verifiable claim (VC) that comprises a digitalsignature; an obtaining module for obtaining, based on the VC, a publickey associated with a second entity; a determining module fordetermining that the digital signature is created based on a private keyassociated with the public key; and a verifying module for verifying theVC based on the determination.

Embodiments disclosed herein have one or more technical effects. In someembodiments, an online platform provides online services forblockchain-based decentralized identity management, such as agentservices and resolver services, and makes such online servicesaccessible to users via API interfaces. This allows control ofoperations related to decentralized identity management (e.g., creationand authentication of decentralized identifiers, issuance andverification of verifiable claims) using programming languages orprotocols other than those required by the blockchain. According to someembodiments, the online platform provides a key management system forcreation and safekeeping of cryptographic keys of users in a securityenvironment. This reduces security risks around users' independentcreation and storage of important identity credentials. In otherembodiments, the online platform provides interfaces and automatedsoftware solutions for an entity to manage identities on behalf of aplurality of other entities. The online platform also includes storageof mapping information between decentralized identities and businessaccounts or service IDs. This facilitates creation of a large number ofdecentralized identifiers or verifiable claims using simplified controlactions as well as effective cross-reference of different identities fora single person or entity. In yet other embodiments, the online platformaggregates and executes certain transactions that would otherwise beexecuted by a blockchain system for decentralized identity management.This reduces the cost and resource consumption of executing thetransactions.

These and other features of the systems, methods, and non-transitorycomputer readable media disclosed herein, as well as the methods ofoperation and functions of the related elements of structure and thecombination of parts and economies of manufacture, will become moreapparent upon consideration of the following description and theappended claims with reference to the accompanying drawings, all ofwhich form a part of this specification, wherein like reference numeralsdesignate corresponding parts in the various figures. It is to beexpressly understood, however, that the drawings are for purposes ofillustration and description only and are not intended as limiting.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a network environment associated with a blockchain inaccordance with some embodiments.

FIG. 2 illustrates a framework for implementing blockchain transactionsin accordance with some embodiments.

FIG. 3 illustrates a network environment associated with a system formanaging decentralized identifiers and verifiable claims in accordancewith some embodiments.

FIG. 4 illustrates an architecture associated with a blockchain-basedsystem for managing decentralized identifiers and verifiable claims inaccordance with some embodiments.

FIG. 5 illustrates a network environment associated with a system forimplementing various examples of functionalities associated withdecentralized identifiers and verifiable claims in accordance with someembodiments.

FIG. 6 illustrates a method for creating a decentralized identifier inaccordance with some embodiments.

FIG. 7 illustrates a method for authenticating a decentralizedidentifier using DID authentication services in accordance with someembodiments.

FIG. 8 illustrates a method for authenticating a decentralizedidentifier using an identity management application in accordance withsome embodiments.

FIG. 9 illustrates a method for issuing a verifiable claim in accordancewith some embodiments.

FIG. 10 illustrates a method for verifying a verifiable claim inaccordance with some embodiments.

FIG. 11 illustrates a method for creating a decentralized identifierusing an agent service in accordance with some embodiments.

FIG. 12 illustrates a method for authenticating a decentralizedidentifier using an agent service in accordance with some embodiments.

FIG. 13 illustrates a method for issuing a verifiable claim using anagent service in accordance with some embodiments.

FIG. 14 illustrates a method for verifying a verifiable claim using anagent service in accordance with some embodiments.

FIG. 15 illustrates a flowchart of a method for creating a decentralizedidentifier in accordance with some embodiments.

FIG. 16 illustrates a flowchart of a method for issuing a verifiableclaim in accordance with some embodiments.

FIG. 17 illustrates a flowchart of a method for verifying a verifiableclaim in accordance with some embodiments.

FIG. 18 illustrates a block diagram of a computer system for creating adecentralized identifier in accordance with some embodiments.

FIG. 19 illustrates a block diagram of a computer system for issuing averifiable claim in accordance with some embodiments.

FIG. 20 illustrates a block diagram of a computer system for verifying averifiable claim in accordance with some embodiments.

FIG. 21 illustrates a block diagram of a computer system in which any ofthe embodiments described herein may be implemented.

DETAILED DESCRIPTION

Embodiments described herein provide methods, systems, and apparatusassociated with an ecosystem for decentralized identity management thatmay provide unique and verifiable identities to entities. Adecentralized identifier (DID) for an entity may allow the entity toobtain full control over its identity as well as information associatedwith the identity. Verifiable claims (VCs) may allow for authorizations,endorsements, and acknowledgements among different entities. In abusiness setting, a service or product provider may use its customers'DIDs and VCs to identify and authenticate the customers and to provideservices or products accordingly.

In some embodiments, a DID may be a unique identifier indicating amapping relationship between a real-world entity and an online identity.The DID may comprise a URL scheme identifier, an identifier for a DIDmethod, and a DID method-specific identifier. Each DID may point to acorresponding DID document. The DID document may comprise descriptivetext in a preset format (e.g., JSON-LD) about the DID and the owner ofthe DID. The DID may serve as a uniform resource identifier (URI) forlocating the DID document. The DID document may comprise variousproperties such as contexts, DID subject, public keys, authentication,authorization and delegation, service endpoints, creation, updates,proof, extensibility, other suitable properties, or any combinationthereof. The DID document may define or point to resources defining aplurality of operations that can be performed with respect to the DID.

In some embodiments, a VC may provide verifiable online informationabout an entity's qualities, characteristics, relationships, and otherrelevant information. A VC may comprise descriptive text in a presetformat (e.g., JSON-LD) that describes one or more declarations regardinga DID (e.g., age of the owner of the DID, educational background of theowner of the DID) and an endorsement of an entity for the declaration. AVC may comprise various properties such as contexts, identifiers, types,credential subject, issuer, issuance date, proofs, expiration, status,presentations, other suitable properties, or any combination thereof.The VC may specify a type of its claim, which may indicate a structureof the claim. This may facilitate automatic processing by the VC issuerand VC verifiers.

Owners of DIDs may participate in the identity management system indifferent roles. For example, an individual may desire to use theservices provided by a business entity, which requires proof that theindividual is over 18 years of age. The individual may be an owner of aDID and may request a VC issued by a government agency that providesverification of citizens' ages. The business entity may verify the VC toascertain that the individual meets the age requirement. In thisscenario, the individual may be a DID owner and a VC holder; thegovernment agency may be a VC issuer, and the business entity may be aVC verifier. As another example, a user may issue a VC to a firstbusiness allowing the first business to use the user's data stored by asecond business. In this case, the user may act as a VC issuer; thefirst business may act as a DID owner and VC holder; the second businessmay act as a VC verifier.

Some embodiments integrate various components, such as blockchainnetworks, cloud applications, agent services, resolver services, userapplications, application programing interface (API) services, keymanagement systems (KMS), and other suitable components, to enablefunctionalities such as creation and authentication of DIDs and issuanceand verification of VCs. In some embodiments, an online platformintegrating one or more of these components may facilitate a businessentity in smoothly creating DIDs and issuing VCs for its users. Thebusiness may interact with the online platform via one or more APIinterfaces and trust a plurality of cryptographic keys to the onlineplatform. The online platform may offer agent services that performvarious operations related to DIDs and VCs on behalf of the businessentity and/or its users. Alternatively, the online platform may provideSDKs that can be integrated into applications of the business entity fordirectly performing operations related to DIDs and VCs.

FIG. 1 illustrates a network environment associated with a blockchain inaccordance with some embodiments. As shown, in the environment 100, aclient 111 may couple to a server end 118, and the server end 118 and aNode B may couple to a blockchain system 112 through variouscommunication networks. Similarly, the server end 118 may optionallycouple to more blockchain systems similar to the blockchain system 112such as blockchain system 113, blockchain system 114, etc. Eachblockchain system may maintain one or more blockchains.

In some embodiments, the client 111 may comprise one or more servers(e.g., Node C) and one or more other computing devices (e.g., Node A1,Node A2, Node A3). Node A1, Node A2, and Node A3 may couple to Node C.In some embodiments, Node C may be implemented by an entity (e.g.,website, mobile phone Application, organization, company, enterprise),which has various local accounts (e.g., local accounts assessed fromNode A1, Node A2, Node A3). For example, a mobile phone Application mayhave millions of end-users accessing the Application's server fromrespective user accounts. The Application's server may correspondinglystore millions of user accounts. The components of the client 111 andtheir arrangement may have many other configurations.

In some embodiments, Node B may include a lightweight node. Alightweight node may not download the complete blockchain, but mayinstead just download the block headers to validate the authenticity ofthe blockchain transactions. Lightweight nodes may be served by andeffectively dependent on full nodes (e.g., blockchain nodes in theblockchain system 112) to access more functions of the blockchain. Thelightweight nodes may be implemented in electronic devices such aslaptops, mobile phones, and the like by installing an appropriatesoftware.

In some embodiments, there may be many more clients coupled to theserver end 118 similar to client 111. The server end 118 may provideBlockchain-as-a-Service (BaaS) and be referred to as a BaaS cloud. Inone embodiment, BaaS is a cloud service model in which clients ordevelopers outsource behind-the-scenes aspects of a web or mobileapplication. BaaS may provide pre-written software for activities thattake place on blockchains, such as user authentication, databasemanagement, and remote updating. The BaaS cloud may be implemented in aserver, server cluster, or other devices. In one embodiment, the BaaScloud provides an enterprise-level platform service based on blockchaintechnologies. This service may help clients to build a secure and stableblockchain environment as well as manage the deployment, operation,maintenance, and development of blockchain easily. Based on the abundantsecurity strategies and multi-tenant isolation of cloud, the BaaS cloudcan provide advanced security protection using chip encryptiontechnologies. Based on highly reliable data storage, this service mayprovide end-to-end and highly available services that can scale upquickly without interruption. The BaaS cloud can provide native supportfor standard blockchain applications and data.

In some embodiments, the blockchain system 112 may comprise a pluralityof blockchain nodes (e.g., Blockchain Node 1, Blockchain Node 2,Blockchain Node 3, Blockchain Node 4, Blockchain Node i, etc.) thatmaintain one or more blockchains (e.g., public blockchain, privateblockchain, consortium blockchain). Other blockchain systems (e.g.,blockchain system 113, blockchain system 114) may comprise similararrangements of blockchain nodes maintaining other blockchains. Eachblockchain node may be found in one or more blockchain systems. Theblockchain nodes of each blockchain system may maintain one or moreblockchains. The blockchain nodes may include full nodes. Full nodes maydownload every block and blockchain transaction and check them againstthe blockchain's consensus rules. The blockchain nodes may form anetwork (e.g., peer-to-peer network) with one blockchain nodecommunicating with another. The order and the number of the blockchainnodes as shown are merely examples for illustration. The blockchainnodes may be implemented in servers, computers, etc. For example, eachblockchain node may be implemented in a server or a cluster of servers.The cluster of servers may employ load balancing. Each blockchain nodemay correspond to one or more physical hardware devices or virtualdevices coupled together via various types of communication methods suchas TCP/IP. Depending on the classifications, the blockchain nodes mayalso be referred to as full nodes, Geth nodes, consensus nodes, etc.

In the environment 100, each of the nodes and devices may be installedwith appropriate software (e.g., application program interface) and/orhardware (e.g., wires, wireless connections) to access other devices ofthe environment 100. In general, the nodes and devices may be able tocommunicate with one another through one or more wired or wirelessnetworks (e.g., the Internet) through which data can be communicated.Each of the nodes and devices may include one or more processors and oneor more memories coupled to the one or more processors. The memories maybe non-transitory and computer-readable and configured with instructionsexecutable by one or more processors to cause the one or more processorsto perform operations described herein. The instructions may be storedin the memories or downloaded over a communications network withoutnecessarily being stored in the memories. Although the nodes and devicesare shown as separate components in this figure, it will be appreciatedthat these nodes and devices can be implemented as single devices ormultiple devices coupled together. For example, Node B may bealternatively integrated into Blockchain Node 2.

The devices such as Node A1, Node A2, Node A3, Node B, and Node C may beinstalled with an appropriate blockchain software to create blockchainaccounts, and initiate, forward, or access blockchain transactions. Theterm “blockchain transaction” may refer to a unit of task executed in ablockchain system and recorded in the blockchain. For example, Node A1may access the blockchain through communications with Node C, the serverend 118, and Blockchain Node 1, and Node B may access the blockchainthrough communications with Blockchain Node 2. In some embodiments, NodeA1 may submit a blockchain account creation request to Node C. Node Cmay forward the request and other similar requests to the server end118. The server end 118 may accordingly create blockchain accounts.

In some embodiments, after receiving a blockchain transaction request ofan unconfirmed blockchain transaction, a recipient blockchain node mayperform some preliminary verification of the blockchain transaction. Forexample, Blockchain Node 1 may perform the preliminary verificationafter receiving a blockchain transaction from Node C. Once verified, theblockchain transaction may be stored in the pool database of therecipient blockchain node (e.g., Blockchain Node 1), which may alsoforward the blockchain transaction to one or more other blockchain nodes(e.g., Blockchain Node 3, Blockchain Node 4). As each blockchain nodemay comprise or couple to a memory, the pool database may berespectively stored in the memories of the blockchain nodes. The pooldatabase may store a plurality of blockchain transactions submitted bythe one or more client devices. After receiving the blockchaintransaction, the one or more other blockchain nodes may repeat theprocess done by the recipient blockchain node.

Each blockchain node may select some of the blockchain transactions fromthe pool according to its preference and form them into a proposed newblock for the blockchain. The blockchain node may perform “mining” ofthe proposed new block by devoting computing power to solve complexmathematical problems. If the blockchain transaction involves ablockchain contract, the blockchain nodes may execute the blockchaincontract locally in respective virtual machines (VMs). To handle theblockchain contracts, each blockchain node of the blockchain network mayrun a corresponding VM and executes the same instructions in theblockchain contract. A VM is a software emulation of a computer systembased on computer architectures and provide functionality of a physicalcomputer. VM in the blockchain context can be understood as a systemdesigned to operate as a runtime environment for blockchain contracts.

A certain blockchain node that successfully mines the proposed new blockof blockchain transactions in accordance with consensus rules may packthe new block into its local copy of the blockchain and multicast theresults to other blockchain nodes. The certain blockchain node may be ablockchain node that has first successfully completed the verification,that has obtained a verification privilege, or that has been chosenbased on another consensus rule, etc. Then, the other blockchain nodesmay follow the same order of execution performed by the certainblockchain node to locally execute the blockchain transactions in thenew block, verify the execution results with one another (e.g., byperforming hash calculations), and synchronize their copies of theblockchain with that of the certain blockchain node. By updating theirlocal copies of the blockchain, the other blockchain nodes may similarlywrite such information in the blockchain transaction into respectivelocal memories. As such, the blockchain contract can be deployed on theblockchain. If the verification fails at some point, the blockchaintransaction is rejected.

The deployed blockchain contract may have an address, according to whichthe deployed contract can be accessed. A blockchain node may invoke thedeployed blockchain contract by inputting certain parameters to theblockchain contract. In one embodiment, Node C or Node B may request toinvoke the deployed blockchain contract to perform various operations.For example, data stored in the deployed blockchain contract may beretrieved. For another example, data may be added to the deployedblockchain contract. For yet another example, a financial transactionspecified in the deployed blockchain contract may be executed.Notwithstanding the above, other types of blockchain systems andassociated consensus rules may be applied to the disclosed blockchainsystem.

FIG. 2 illustrates a framework for implementing blockchain transactionsin accordance with some embodiments. In some embodiments, the client 111may transmit information (e.g., a request with relevant information forcreating a blockchain account) to the server end 118 for the server end118 to create a blockchain account. To this end, the server end 118 maygenerate cryptography keys, compile the request with other accountcreation requests, and/or perform other operations. Then, the server end118 may transmit a blockchain transaction (e.g., blockchain transactionA) including the compiled account creation requests to one or more ofblockchain nodes for execution.

In some embodiments, Node B may construct a signed blockchaintransaction and transmit it to one or more blockchain nodes forexecution. In one embodiment, Node B may construct a blockchaintransaction B. The blockchain transaction B may comprise a blockchaincontract B for deployment or invoking a deployed blockchain contract.For example, the blockchain transaction B may comprise a blockchaincontract that creates a blockchain account or invokes a deployedblockchain contract A. The blockchain contract B may be programmed insource code at a user-end application 221. For example, a user ormachine may program the blockchain contract B. Node B may compile thesource code using a corresponding compiler, which converts the sourcecode into bytecode. The blockchain transaction B may compriseinformation such as nonce (e.g., transaction serial number), from (e.g.,a blockchain address of Node B or another blockchain address), to (e.g.,empty if deploying a blockchain contract), transaction fee, value (e.g.,transaction amount), signature (e.g., signature of Node B), data (e.g.,message to a contract account), etc. The Node B may send the blockchaintransaction B to one or more blockchain nodes through a remote procedurecall (RPC) interface 223 for execution. RPC is a protocol that a firstprogram (e.g., user-end application) can use to request a service from asecond program located in another computer on a network (e.g.,blockchain node) without having to understand the network's details.When the first program causes a procedure to execute in a differentaddress space, it is as if a normal (local) procedure call, without theprogrammer explicitly coding the details for the remote interaction.

In some embodiments, on receiving the blockchain transaction (e.g.,blockchain transaction A or B), the recipient blockchain may verify ifthe blockchain transaction is valid. For example, the signature andother formats may be verified. If the verification succeeds, therecipient blockchain node may broadcast the received blockchaintransaction (e.g., blockchain transaction A or B) to the blockchainnetwork including various other blockchain nodes. Some blockchain nodesmay participate in the mining process of the blockchain transactions.The blockchain transaction may be picked by a certain node for consensusverification to pack into a new block. If the blockchain transactioninvolves a blockchain contract, the certain node may create a contractaccount for a blockchain contract in association with a contract accountaddress. If the blockchain transaction involves invoking a deployedblockchain contract, the certain node may trigger its local VM toexecute the received blockchain transaction, thereby invoking thedeployed blockchain contract from its local copy of the blockchain andupdating the account states in the blockchain. If the certain nodesucceeds in mining a new block, the certain node may broadcast the newblock to other blockchain nodes. The other blockchain nodes may verifythe new block as mined by the certain blockchain node. If consensus isreached, the blockchain transaction B is respectively packed to thelocal copies of the blockchain maintained by the blockchain nodes. Theblockchain nodes may similarly trigger their local VMs to execute theblockchain transaction B, thus invoking the blockchain contract Adeployed on the local copies of the blockchain and making correspondingupdates.

Upon receiving the new block, the other blockchain nodes may performverifications. If a consensus is reached that the new block is valid,the new block is respectively packed to the local copies of theblockchain maintained by the blockchain nodes. The blockchain nodes maysimilarly trigger their local VMs (e.g., local VM 1, local VM i, localVM 2) to execute the blockchain transactions in the new block, thusinvoking local copies of the blockchain (e.g., local blockchain copy 1,local blockchain copy i, local blockchain copy 2) and makingcorresponding updates. The hardware machine of each blockchain node mayhave access to one or more virtual machines, which may be a part of orcouple to the corresponding blockchain node. Each time, a correspondinglocal VM may be triggered to execute the blockchain transaction.Likewise, all other blockchain transactions in the new block will beexecuted. Lightweight nodes may also synchronize to the updatedblockchain.

FIG. 3 illustrates a network environment associated with a system formanaging decentralized identifiers and verifiable claims in accordancewith some embodiments. In some embodiments, a user-side system 310 maycorrespond to an entity. The entity may be a business entity thatprovides one or more products or services to a plurality of users. Theentity may also be an individual user, a group of users, anorganization, other suitable entities, or any combination thereof. Theuse-side system 310 may comprise a plurality of computer systems, datastores, cloud services, mobile applications, other suitable components,or any combination thereof. The user-side system 310 may comprise aserver 311 and a database 313. The database 313 may store dataassociated with a plurality of user accounts of the users of the entity.The entity corresponding to the user-side system 310 may desire tocreate and manage DIDs and VCs for itself as well as its users. It maycomprise one or more software development kits (SDKs) 312 for managingcreation and authentication of DIDs or issuance and verification of VCs.

In some embodiments, to implement functionalities associated with DIDsand VCs, the user-side system 310 may interface with a service-sidesystem 320. In some embodiments, the service-side system 320 asillustrated in FIG. 3 may be equivalent to, be part of, or comprise oneor more components of the server end 118 as illustrated in FIGS. 1 and2. The service-side system 320 may comprise one or more agents 321, oneor more resolvers 322, one or more key management systems 323, one ormore clouds 324, other suitable components or any combination thereof.The agent 321 may provide various services or applications related toDIDs or VCs and maintain databases mapping account information or otherbusiness data from the user-side system 310 to DIDs, VCs, or otherinformation or data stored on one or more blockchains. The agent 321 mayprovide one or more application programming interfaces (APIs), which maybe used by the user-side system 310 to directly submit requests relatedto DIDs or VCs. The agent 321 may manage communications between theuser-side system 310 and the resolver 322 and the cloud 324.

In some embodiments, the agent 321 may be coupled to a key managementsystem (KMS) 323. The KMS 323 may generate, distribute, and managecryptographic keys for devices and applications. It may cover securityaspects from secure generation of keys over the secure exchange of keysto secure key handling and storage. The functionalities of the KMS 323may include key generation, distribution, and replacement as well as keyinjection, storing, and management. The KMS 323 may comprise or becoupled to a trusted execution environment (TEE). The TEE may be anisolated area on the main processor of a device that is separate fromthe main operating system. The TEE may provide an isolated executionenvironment offering security features such as isolated execution,integrity of applications executing with the TEE, along withconfidentiality of their assets. It may guarantee code and data loadedinside to be protected with respect to confidentiality and integrity. Insome embodiments, the KMS 323 may generate one or more cryptographic keypairs in the TEE. Before outputting the cryptographic key pair, the TEEmay encrypt the private key. The encryption of the private key can bebased on various methods or standards, such as Data Encryption Standard(DES), TripleDES, RSA, Advanced Encryption Standard (AES), Twofish, etc.The KMS 323 may store the encrypted private key in association with thepublic key. To use the private key, the KMS 323 may feed the encryptedprivate key to the TEE for decryption and processing.

In some embodiments, the agent 321 may be coupled to a resolver 322,which may comprise software applications for managing interactionsbetween the agent and a blockchain 330 in transactions related to DIDsor VCs (e.g., correspondence between a DID and a DID document). Theresolver 322 may be part of or coupled to the one or more cloud-basedservices. The one or more cloud-based services may be associated with ablockchain-as-a-service (BaaS) cloud 324 or other suitable cloudservices. The BaaS cloud 324 may constitute a platform that offersvarious interfaces to one or more blockchains 330. It may receive inputsfrom an external application and facilitate the creation and executionof operations such as blockchain transaction deployment, blockchaincontract creation and execution, blockchain account creation based onthe inputs. The BaaS cloud 324 may also obtain information and data fromone or more blockchains 330 and feed the information and data to one ormore other systems using the BaaS cloud 324. In some embodiments, theagent 321 may be directly coupled to the cloud 324 to use its services.In some embodiments, one or more of the agent 321, the resolver 322, andthe KMS 323 may be integrated as part of the BaaS cloud 324 or anothersuitable online platform.

In some embodiments, the resolver 322 and cloud 324 may be coupled to ablockchain 330. The blockchain 330 may comprise one or more blockchaincontracts 331. One or more of the blockchain contracts 331 may beconfigured to be executed by a virtual machine associated with theblockchain 300 to perform one or more operations associated with DIDsand VCs. The operations may comprise creating a new DID, storing a DIDdocument, updating a DID document, identifying a DID document based on aDID, storing information associated with a VC, retrieving informationassociated with a VC, other suitable operations, or any combinationthereof. The resolver 322 and cloud 324 may be configured to deploy oneor more transactions on the blockchain 330 that invoke one or more ofthe blockchain contracts 331. The transactions may trigger one or moreoperations related to DIDs and VCs.

FIG. 4 illustrates an architecture associated with a blockchain-basedsystem for managing decentralized identifiers and verifiable claims inaccordance with some embodiments. In some embodiments, the system maycomprise three main components, one or more agent services 321, one ormore resolver services 322, and one or more blockchain contracts 331.The one or more agent services 321 may be configured to process requestsrelated to DIDs and VCs that are received from users. The one or moreagent services 321 may manage mapping relationships between accountinformation on user-side systems 310 and DIDs of the owners of theaccounts. The agent services 321 may comprise a DID agent service API410 for receiving DID-related requests from user-side systems 310.Depending on the nature of a request, it may be fed to a user agent 411for performing operations such as creation and authentication of DIDs oran issue agent 412 for performing operations such as issuance of VCs.The requests from a party desiring to verify a VC may be fed to theverifier agent 413. The one or more agent services 321 may also providea verifiable claim repository 414 for storing one or more VCs. The agentservices 321 may also use one or more memories 415 and one or moredatabases 416. The agent services 321 may be coupled to a KMS 323 and aBaaS Cloud 324. The agent services 321 may be coupled to the resolverservices 322.

In some embodiments, one or more agents of the agent services 321 maysend one or more requests to a DID resolver API 420 associated with theresolver services 322. The resolver services 322 may be configured toprocess interactions between the agent services 321 and the blockchain330. The resolver services 322 may perform operations such as obtainingdata from the blockchain 300, adding data to the blockchain 330,creating blockchain contracts 331, deploying transaction to theblockchain 330 to invoke blockchain contracts 331, other suitableoperations, or any combination thereof. The resolver services 322 maycomprise a DID resolver 421 configured to manage DIDs and DID documentsstored on the blockchain 330 and a VC resolver 422 configured to manageVCs for DIDs created based on the blockchain 330. The resolver services322 may also comprise a listener 424 for obtaining data from theblockchain 331. The listener 424 may store obtained data to a database423. The data may be used by the DID resolver 421 and the VC resolver422. The DID resolver 421, VC resolver 422, and listener 424 may becoupled to a BaaS cloud 324 for interactions with the blockchain 330.

In some embodiments, the blockchain 330 may comprise one or moreblockchain contracts (331 a, 331 b, 331 c) for managing DIDs and DIDdocuments and comprise one or more contracts (331 d, 331 e, 331 f) formanaging VCs. The contracts may be executed by one or more virtualmachines associated with the blockchain 330 to perform operations suchas creating DIDs, storing DID documents, updating DID documents, storinginformation associated with VCs, other suitable operations, or anycombination thereof.

FIG. 5 illustrates a network environment associated with a system forimplementing various examples of functionalities associated withdecentralized identifiers and verifiable claims in accordance with someembodiments. Components of the network environment may be categorizedinto three layers 510, 520, and 530. In some embodiments, the bottom orcore layer 510 may comprise one or more blockchains 330, which maycomprise one or more blockchain contracts (331 g, 331 h, 331 i) that canbe executed to perform operations related to DIDs and VCs. Theblockchain 330 may store a plurality of DIDs and a plurality of DIDdocuments corresponding to the DIDs. The blockchain contracts (331 g,331 h, 331 i) may be configured to manage mapping relationships betweenDIDs and DID documents, as well as creation and changes to DIDdocuments. The blockchains 330 may be accessible to one or moreresolvers (322 a, 322 b) for operations related to DIDs and VCs. Theresolvers (322 a, 322 b) may be configured to provide to an externalsystem services such as searching for DID documents or data contained inDID documents based on inputted DIDs. One or more method libraries 511may also be available for external systems to adopt to interact with theblockchain 330.

In some embodiments, the middle or enhancement layer 520 may compriseone or more user agents 411, one or more issuer agents 412, or one ormore verifier agents 413. In some embodiments, the blockchain 330 maycomprise a consortium blockchain, which may or may not be directlyaccessible to users that are not consensus nodes of the consortiumblockchain. A user agent 411 may provide an interface for an ordinaryuser to interact with the blockchain. In some embodiments, the useragent 411 may be configured to create one or more DIDs, authenticate oneor more DIDs, interact with one or more verifiable data registry 521 orone or more DID hubs 522, send notifications to an owner of a DID,perform other suitable functionalities, or any combination thereof.Here, a DID hub 522 may comprise a system in which an owner of a DIDstores its sensitive data. The owner may grant certain other entities(e.g., institutions issuing verifiable claims) access to data stored inthe DID hub 522. A verifiable data registry 521 may comprise a VCrepository for storing and managing the VCs issued to an owner of a DID.An issuer agent 412 may comprise one or more APIs (e.g., REST API) orSDKs. The issuer agent 412 may be configured to issue one or moreverifiable claims, withdraw one or more verifiable claims, check andinspect an existing verifiable claim, publish a template for verifiableclaims, maintain a template for verifiable claims, perform othersuitable operations, or any combination thereof. A verifier agent 413may comprise one or more APIs (e.g., REST API) or SDKs and be configuredto verify a verifiable claim or perform one or more other suitableoperations. In some embodiments, the layer 520 may also comprise one ormore code libraries (e.g., DID resolve library 523, DID authenticationlibrary 524) that can be adopted and used to interact with the DIDresolvers 322 or directly with the blockchain 330. The code librariesmay be packaged into one or more SDKs and be used to performfunctionalities such as DID authentication, interactions with theblockchain 300, or interfacing with blockchain contracts 331. The issueragent 412 and verifier agent 413 may be used by key participants in thenetwork environment associated with DIDs and VCs such as entities ableto perform know-your-customer (KYC) authentication or endorsement forusers or to issue or verify verifiable claims (e.g., governmentinstitutions, banks, financial service providers). The key participantsmay provide third-party services that can be integrated via connectionswith the issuer agent 412, the verifiable agent 413, or other suitablecomponents of the network environment.

In some embodiments, the upper or extension layer 530 may comprise oneor more external services or applications related to DIDs and VCs. Theservices or applications may comprise one or more issuer applications531, one or more verifier applications 532, an identity managementapplication 533, a service application 534, one or more other suitableservices or applications, or any combination thereof. An issuerapplication 531 may correspond to an entity (e.g., governmentinstitution, banks, credit agency) issuing verifiable claims signed orendorsed by the entity for users. The issuer application 531 may operateon a user-side system 310. The issuer application 531 may comprise anissuer verifiable claim manager service which may allow an issuer tomanage issued VCs, maintain their status (e.g., validity), or performother suitable operations. The issuer application 531 may interact withthe layers 510 and 520 via a connection or interface with the issueragent 412 or one or more code libraries 523 and 524. A verifierapplication 532 may correspond to an entity (e.g., service provider,credit issuer) needing to verify verifiable claims to ascertain a user'sinformation (e.g., identity, age, credit score). The verifierapplication 532 may operate on a user-side system 310. The verifierapplication 532 may interact with layers 510 and 520 via a connection orinterface with the verifier agent 413 or one or more code libraries 523and 524. The identity management application 533 may be installed on aclient device or terminal associated with a user. The user may be a DIDowner, which may be an individual, a business, an organization, anapplication, or any other suitable entity. The identity managementapplication 533 may allow a user to manage cryptographic key pairsassociated with DIDs, original data, or VCs, to receive notificationsfrom a user agent 411, to authenticate a DID, to grant access to data,to use a VC, to perform other suitable operations, or any combinationthereof. The identity management application 533 may interact with thelayers 510 and 520 via a connection or interface with the user agent411. The service application 534 may also be coupled to the user agent411 and be configured to manage functions related to DIDs or VCs for oneor more users or accounts.

FIGS. 6-10 illustrate example operations associated with DIDs or VCsperformed by one or more user-side systems 310, one or more resolvers322, one or more clouds 324, or one or more blockchain systems 330. Insome embodiments, a user-side system 310 may manage one or more DIDs orone or more VCs by interfacing with a DID resolver 322 and a blockchain330 storing DIDs and DID documents. The user-side system 310 may use oneor more SDKs 312 for managing DIDs that are compatible with methodsassociated with the DIDs. The SDKs 312 may be integrated with one ormore applications used by the user-side system 310. The user-side system310 may also interface with one or more service endpoints for storingverifiable claims, one or more service endpoints for storing statusinformation for verifiable claims, one or more service endpoints forauthentication of DIDs, other suitable systems, or any combinationthereof.

FIG. 6 illustrates a method for creating a decentralized identifier inaccordance with some embodiments. The operations of the method presentedbelow are intended to be illustrative. Depending on the implementation,the method may include additional, fewer, or alternative steps performedin various orders or in parallel. The method may start at step 602, inwhich a server 311 of a user-side system 310 may obtain identityauthentication for a user for whom it is going to obtain a DID. Theuser-side system 310 may also generate or retrieve a cryptographic keypair including a public key and a private key for use to create the DID.At step 604, the server may invoke a functionality of an SDK 312 forcreating a new DID. Here, at least a public key of the cryptographic keypair may be inputted or otherwise made available to the SDK 312. At step606, the user-side system 310 may send a request for creating a new DIDto the resolver 322 using the SDK 312. At step 608, the resolver 322 maysend a request to a blockchain system 330 for creating a new blockchainaccount. Here, the request may be directly sent to one or moreblockchain nodes of the blockchain 330 in the form of one or moreblockchain transactions or be sent to a BaaS Cloud 324 or other suitableinterface systems associated with a blockchain 330. In response to therequest from the resolver 322, at step 610, the resolver 322 may obtainan indication that a new blockchain account has been created from thecloud 324. The blockchain account may be associated with an address onthe blockchain 330. The information obtained by the resolver 322 maycomprise information associated with the newly-created blockchainaddress. It may comprise a newly-created DID or at least informationsufficient to construct the DID. At step 612, the resolver 322 may senda message back to the SDK 312 associated with the user-side system 310.The message may comprise information associated with the newly createdDID.

In some embodiments, a DID document may be created and stored on theblockchain 330. At step 614, the user-side system may use the SDK 312 togenerate a DID document and add the public key associated with thenewly-created DID and authentication information to the DID document. Atstep 616, the user-side system 310 may use the SDK 312 to addinformation associated with one or more service endpoints (e.g.,information associated with an authentication service endpoint,information associated with a verifiable claim repository) to the DIDdocument. The authentication service endpoint and the verifiable claimrepository may be provided as part of a system including the resolver322 or be provided by third-party systems. Then, at step 618, theuser-side system may use the SDK 312 to generate one or more blockchaintransactions for storing the DID document to the blockchain 330. Theuser-side system 310 may also use the SDK 312 to generate a hash valueof the blockchain transaction and generate a digital signature for thetransaction using the private key associated with the DID. At step 620,the SDK 312 may send the DID document as well as the blockchaintransaction to the DID resolver 322 for sending to the blockchainsystem. At step 622, the DID resolver may send one or more transactionsto the blockchain system (e.g., one or more blockchain nodes, a BaaSCloud 324). The one or more transactions may invoke a blockchaincontract 331 for managing DIDs and DID documents on the blockchain 330.At step 624, the resolver 322 may obtain information from the blockchain330 indicating that the DID document has been successfully stored. Atstep 626, the resolver 322 may forward a confirmation to the SDK 312. Atstep 628, the SDK 312 may send information associated with the createdDID and DID document to the server 311 of the user-side system 310,which may then send a notification to the user confirming successfulcreation of the DID at step 630.

FIG. 7 illustrates a method for authenticating a decentralizedidentifier using DID authentication services in accordance with someembodiments. The operations of the method presented below are intendedto be illustrative. Depending on the implementation, the method mayinclude additional, fewer, or alternative steps performed in variousorders or in parallel. In some embodiments, a user owning a DID may useDID authentication services provided by a business entity to achieveauthentication of its ownership of the DID. The owner may trust apublic-private key pair corresponding to the DID to the business entityfor storage. The owner may provide a network location (e.g., identifiedby a URL) of the DID authentication services as a service endpoint forauthentication of the DID. The location identifier of the DIDauthentication services may be included in a “service” filed of the DIDdocument associated with the DID.

In some embodiments, a verifier 532 (e.g., a service provider needing toverify information of a customer) may initiate a DID authenticationprocess using an SDK 312. At step 702, the verifier 532 may obtain theDID provided by a purported owner. At step 704, the verifier 532 maycall the SDK 312 to create a DID authentication challenge. The verifier532 may input to the SDK 312 the DID to be authenticated and a networkaddress (e.g., a URL) to which a response to the challenge is to besent. At step 706, the SDK 312 may send a query to a resolver 322 forthe DID document associated with the DID to be authenticated. At step708, the resolver 322 may formulate a blockchain transaction invoking ablockchain contract 331 for managing DIDs and send the blockchaintransaction to one or more blockchain nodes associated with theblockchain 330 for execution. As a result, the resolver 322 may obtainthe DID document corresponding to the DID at step 710 and forward it tothe SDK 312 at step 712. At step 714, the verifier 532 may use the SDK312 to create a DID authentication challenge based on the obtained DIDdocument. In some embodiments, the DID authentication challenge maycomprise a ciphertext created by encrypting original text using a publickey associated with the DID that is recorded in the DID document. Thechallenge may also comprise a network address to which a response is tobe sent. At step 716, the verifier 532 may obtain information associatedwith the authentication service endpoint for the DID from the DIDdocument. At step 718, the verifier 532 may use the SDK 312 to send thechallenge to the DID authentication services associated with the DID.

In some embodiments, after obtaining the DID authentication challengefrom the verifier 532, the DID authentication services may obtainconsent from the owner for such authentication request at step 720. Ifthe owner provides consent or permission for the identityauthentication, the DID authentication services may call its version ofthe SDK 312 to create a response to the DID authentication challenge atstep 722. In some embodiments, the response to the DID authenticationchallenge may comprise plaintext that is the result of decrypting theciphertext in the challenge using the private key associated with theDID. The SDK 312 may return the response to the DID authenticationservices at step 724, which may then send the response to the networkaddress provided by the verifier 432 at step 726. Upon receiving theresponse to the DID authentication challenge, the verifier 532 may callits SDK 312 at step 728 to check the response. At step 730, the SDK 312may determine whether the response proves that the user providing theDID is the owner of the DID. In some embodiments, the SDK 312 may checkthe response by comparing decrypted text in the response with theoriginal text that was used to create the DID authentication challenge.If the response is determined to be correct, the SDK 312 may return amessage to the verifier 532 indicating the DID is a valid proof ofidentity of the user at step 732. At step 734, the verifier 532 maynotify the user as to the validity of the DID.

FIG. 8 illustrates a method for authenticating a decentralizedidentifier using an identity management application in accordance withsome embodiments. The operations of the method presented below areintended to be illustrative. Depending on the implementation, the methodmay include additional, fewer, or alternative steps performed in variousorders or in parallel. In some embodiments, a user may use a terminalfor managing DIDs, which may comprise an identity management applicationor another suitable application. The application may comprise a versionof the SDK 312. In this example, the user may need services from aservice provider (i.e., verifier), which requires verification that theuser owns a particular DID in order to provide its services. The usermay send a service request to the verifier. The service request may bein the form of an HTTP request.

At step 802, the user may call the identity management application toprovide authentication information for the service request. The user mayprovide the original service request as an input to the SDK 312 includedin the identity management application. At step 804, the SDK 312 maysign the content of the original service request using a private key ofa cryptographic key pair associated with the DID. The SDK 312 may beused to add the DID and a digital signature for the original servicerequest to the original service request to create a signed servicerequest. In case the original service request is a HTTP request, the SDK312 may add the DID and the digital signature to a header of the HTTPrequest. At step 806, the SDK 312 may send the signed service request tothe verifier 532.

In some embodiments, the verifier 532 may call its version of an SDK 312to authenticate the DID included in the signed service request at step808. At step 810, the SDK 312 may obtain the DID and the digitalsignature included in the signed service request. In case the signedservice request is an HTTP request, the DID and the digital signaturemay be obtained from the header of the HTTP request. At step 812, theSDK 312 may send a query to a resolver 322 for the DID documentassociated with the DID to be authenticated. At step 814, the resolver322 may formulate a transaction invoking a blockchain contract 331 formanaging DIDs and send the transaction to one or more blockchain nodesassociated with the blockchain 330 for execution. As a result, theresolver 322 may obtain the DID document corresponding to the DID atstep 816 and forward it to the SDK 312 at step 818. At step 820, the SDK312 associated with the verifier 532 may check the signed servicerequest to determine whether it is from the owner of the DID based onthe obtained DID document. In some embodiments, the SDK 312 may sign thecontent of the service request using a public key obtained from DIDdocument, and check the resulting signature against the digitalsignature included in the signed service request to determine if thepublic key is associated with the key used to create the digitalsignature in the signed service request. If so, the SDK 312 maydetermine that the service request from the user is valid. It may thensend it to the verifier 532 for processing at step 822. The verifier 532may process the service request and provide appropriate services to theuser at step 824. Then, the verifier 532 may send a response to the userat step 826 to confirm completion of the requested services.

FIG. 9 illustrates a method for issuing a verifiable claim in accordancewith some embodiments. The operations of the method presented below areintended to be illustrative. Depending on the implementation, the methodmay include additional, fewer, or alternative steps performed in variousorders or in parallel. In some embodiments, an issuer 531 may issue a VCto a user. The VC may be used as a proof of certain facts orcharacteristics of the user as endorsed by the issuer 531.

At step 902, the issuer 531 may obtain a DID associated with the userand a proof of the fact to be included in the VC. Here, the proof of thefact to be included in the VC may be based on materials submitted by theuser to the issuer 531, information or data obtained by the issuer 531from third-party systems, in-person verification of the facts, othersuitable sources of proof, or any combination thereof. After obtainingthe DID and the proof, the issuer 531 may call an SDK 312 associatedwith creation of VCs to initiate a process for creating the VC at step904. The message from the issuer 531 may comprise a statement of theproven fact or a claim about the user. The SDK 312 may create a VCdocument including the statement using a cryptographic key pairassociated with the issuer 531. In some embodiments, the VC may includea digital signature created based on a private key associated with theissuer 531. At step 908, the SDK 312 may update a locally-stored statusof the VC.

At step 910, the SDK 312 may send a query to a resolver 322 for the DIDdocument associated with the DID for which the VC is issued. At step912, the resolver 322 may formulate a transaction invoking a blockchaincontract 331 for managing DIDs and send the transaction to one or moreblockchain nodes associated with the blockchain 330 for execution. As aresult, the resolver 322 may obtain the DID document corresponding tothe DID at step 914 and forward it to the SDK 312 at step 916. At step918, the SDK 312 may identify a VC service endpoint associated with theDID of the user for storing VCs. The VC service endpoint may correspondto a VC repository 414 used by the user or the owner of the DID. Then atstep 920, the issuer may use the SDK 312 to send the VC to the VCrepository 414 for storage. The VC may also include informationassociated with a VC status service endpoint, which may store andprovide status information for the VC. In some embodiments, theinformation may comprise a network address (e.g., URL) for an issueagent service used by the issuer 531 to keep status of VCs. The VCstatus service endpoint may or may not be associated with the VCrepository 414. The SDK 312 may provide the current status of the newlygenerated VC to the VC status service endpoint for storing. The statusof the VC may be stored on a blockchain.

FIG. 10 illustrates a method for verifying a verifiable claim inaccordance with some embodiments. The operations of the method presentedbelow are intended to be illustrative. Depending on the implementation,the method may include additional, fewer, or alternative steps performedin various orders or in parallel. In some embodiments, a user mayprovide a VC to another party (e.g., a verifier 532) to prove a factstated in the VC. The VC may be provided after the verifier 532 hasverified that the user is the owner of a DID associated with the VC.

At step 1002, the verifier 532 may call an SDK 312 comprising codelibraries associated with VC verification to verify the VC. The SDK 312may identify from the VC (e.g., in a “credential status” field)information associated with a VC status service endpoint for the VC. TheVC status service endpoint may be associated with an issuer 531. At step1004, the SDK 312 may send a query to the issuer 531 for the status ofthe VC. In response, at step 1006, the issuer 531 may call an SDK 312 toobtain the status of the VC. The SDK 531 may obtain the status of theVC. As an example, the SDK 312 may determine that the VC has a validstatus and may return the information to the issuer 531 at step 1008.Then, at step 1010, the issuer may return the valid status informationto the SDK 312 associated with the verifier 532.

The verifier 532 may obtain an identifier associated with the issuer 531of the VC. For example, the identifier may be a DID of the issuer 531.At step 1012, the SDK 312 may send a query to a resolver 322 for apublic key associated with the DID of the issuer 531 of the VC. At step1014, the resolver 322 may formulate a transaction invoking a blockchaincontract 331 for managing DIDs and send the transaction to one or moreblockchain nodes associated with the blockchain 330 for execution. As aresult, the resolver 322 may obtain the public key corresponding to theDID at step 1016 and forward it to the SDK 312 associated with theverifier 532 at step 1018. At step 1020, the SDK 312 associated with theverifier 532 may verify the VC based on a digital signature includedtherein and the public key associated with the issuer 531 of the VC. Ifthe VC is verified, the SDK 312 may send a confirmation to the verifier532 at step 1022.

FIGS. 11-14 illustrate example operations associated with DIDs or VCsperformed by one or more user-side systems 310, one or more agents 321,one or more resolvers 322, one or more clouds 324, one or moreblockchain systems 330, one or more KMSs, or other suitable systems,applications, services. In some embodiments, a user-side system 310 maymanage one or more DIDs or VCs by interacting with an online platformintegrating one or more of the aforementioned components via one or moreAPI interfaces (e.g., REST API). The user-side system 310 may trustconfidential information such as cryptographic key pairs to the onlineplatform for secure keeping.

FIG. 11 illustrates a method for creating a decentralized identifierusing an agent service in accordance with some embodiments. Theoperations of the method presented below are intended to beillustrative. Depending on the implementation, the method may includeadditional, fewer, or alternative steps performed in various orders orin parallel. In some embodiments, a user-side system 310 associated withan entity may use one or more agent services 321 to create one or moreDIDs for one or more users of the entity and correlate the DIDs withinternal accounts or identifications (e.g., service IDs) maintained bythe entity. In order to create DIDs for its users, the entity may havebeen authenticated by the online platform as a trusted entity and mayhave made a commitment to provide truthful information. In someembodiments, the entity may have been issued a VC by a bootstrap issuerDID to certify that it is authenticated by an authoritative entity. Theentity may be required to authenticate the identities of its users. Theuser-side system 310 may use one or more KMSs 323 and the secureenvironment (e.g., TEE) that they provide to manage cryptographic keysassociated with the created DIDs and to map the cryptographic keys tothe internal accounts or identifications maintained by the entity. Withthe help of the agent services 321, the user-side system 310 may useservices associated with DIDs without keeping a record of the DIDs.Instead, it may simply provide its internal account information oridentification information for identification of the DIDs via one ormore interfaces associated with the agent services 321.

In some embodiments, an online platform for managing DIDs may receive arequest for creating a DID. The request may be from a first entity onbehalf of a second entity for creating the DID for the second entity. Inthe example illustrated by FIG. 11, an entity (e.g., first entity) maycreate a DID for a user (e.g., second entity), who may have an accountwith the business entity. In some embodiments, the entity mayauthenticate the identity of a user before creating a DID for the user.For example, at step 1102 of FIG. 11, a server 311 of a user-side system310 associated with the entity may perform identity authentication orotherwise obtain identity authentication information for the user. Theentity may have authenticated the identity of the user earlier and maymaintain such information in a database. At step 1002, the server 311may retrieve such information. Then, at step 1004, the server 311 maysend the request for creating the DID to an agent service API 410associated with a user agent 411 associated with the online platform.The request may comprise an account identifier corresponding to theuser. The request may take the form of an API message. At step 1006, theagent service API 410 may send a request to a user agent 411 forcreating the DID.

At step 1108, the user agent 411 may check the request for requiredinformation. In some embodiments, to create a DID for a user, the entitymay be required to have an existing DID for itself. The user agent 411may check the request to determine that the sender of the request has anexisting DID and to determine the DID associated with the sender. Insome embodiments, the entity may be required to provide a proof ofidentity authentication for the user. The proof of identityauthentication may comprise a proof of real-person authentication, aproof of real-name authentication, another suitable proof ofauthentication, or any combination thereof. For example, a proof ofreal-name authentication may be based on a user's office identification(e.g., government-issued ID). An example proof may, for example, be anumber created by applying a hash function (e.g., SHA-256) to acombination of an ID type, ID number, and a number of the user. Such aproof may ensure unique correspondence with a particular user whilemaintaining sensitive information of the user confidential. The useragent 411 may determine whether the request comprises a proof ofidentity authentication and, if so, accept the request. The user agent411 may reject the request if it does not comprise the proof of identityauthentication or may send a request to the entity for a proof ofidentity authentication. The user agent 411 may obtain the proof ofidentity authentication based on the received request, which maydirectly comprise the proof or information associated with means toobtain the proof. If the request comprises the required information, theuser agent 411 may create a key alias corresponding to the proof ofidentity authentication for the user at step 1110.

In some embodiments, the user agent 411 may obtain, in response toreceiving the request, a public key of a cryptographic key pair. Thepublic key may later be used as a basis for creating the DID. In someembodiments, the user agent 411 may obtain the public key from the KMS323. At step 1112, the user agent 411 may send a request to the KMS 323for generating and storing a cryptographic key pair. The KMS 323 maygenerate a cryptographic key pair. In some embodiments, the KMS 323 maycause the cryptographic key pair to be generated in a TEE associatedwith the KMS 323. After the key pair is generated, the KMS 323 mayobtain a public key and an encrypted private key from the TEE. At step1114, the KMS 323 may send the public key to the user agent 411.

In some embodiments, the online platform may obtain the DID based on thepublic key. At step 1116, the user agent 411 may send a request forcreating anew DID to the resolver 322 The request may comprise thepublic key. In response, the resolver 322 may generate, based on thepublic key, one or more blockchain transactions for creating the DID andadding a DID document associated with the DID to a blockchain.Alternatively, the DID resolver may send a request to the BaaS cloud 324for generation of such transactions. For example, at step 1118, theresolver 322 may send a request to a blockchain system 330 for creatinga new blockchain account. Here, the request may be directly sent to oneor more blockchain nodes of the blockchain 330 in the form of one ormore blockchain transactions or be sent to a BaaS Cloud 324 or othersuitable interface systems associated with a blockchain 330. Theblockchain transactions may invoke one or more blockchain contractsconfigured for managing DIDs. In response to the request from theresolver 322, at step 1120, the DID resolver may obtain an indicationfrom the blockchain 330 or the cloud 324 that a new blockchain accountis successfully created. The blockchain account may be associated withan address on the blockchain 330. Information obtained by the resolver322 may comprise information associated with the newly-createdblockchain address. It may directly comprise a newly-created DID or atleast information sufficient to construct the DID. At step 1122, theresolver 322 may send a message back to the user agent 411. The messagemay comprise information associated with the newly created DID.

In some embodiments, a DID document may be created and stored in theblockchain 330. At step 1124, the user agent 411 may generate a DIDdocument and add the public key associated with the newly-created DIDand authentication information to the DID document. At step 1126, theuser agent 411 may add information associated with one or more serviceendpoints (e.g., information associated with an authentication serviceendpoint, information associated with a verifiable claim repository) tothe DID document. The authentication service endpoint and the verifiableclaim repository 414 may be provided as part of the online platform. TheDID document may comprise one or more public keys associated with theobtained DID, authentication information associated with the obtainedDID, authorization information associated with the obtained DID,delegation information associated with the obtained DID, one or moreservices associated with the obtained DID, one or more service endpointsassociated with the obtained DID, a DID of a creator of the obtainedDID, other suitable information, or any combination thereof. In someembodiments, the DID document may comprise a “creator” field containingidentification information (e.g., DID) of the entity that sent therequest for creating the DID on behalf of the user. The “creator” fieldmay serve as a record of the entity that authenticated of the identityof or endorsed the owner of the DID. Then, at step 1128, the user agent411 may generate one or more blockchain transactions for storing the DIDdocument to the blockchain 330. The user agent 411 may also generate oneor more hash values of the blockchain transactions.

In some embodiments, for the one or more blockchain transactions to beexecuted by one or more nodes of the blockchain 330, they are requiredto be signed using the private key associated with the DID. The useragent 411 may obtain such a digital signature from the KMS 323. At step1130, the user agent 411 may send a request to the KMS 323 for signing ablockchain transaction using the private key of the cryptographic keypair associated with the DID. The request may comprise the hash value ofthe transaction and a public key associated with the DID. The KMS 323may create a digital signature for the transaction. In some embodiments,the digital signature may be generated in a TEE associated with the KMS323. The KMS 323 may identify an encrypted private key associated withthe public key and feed the encrypted private key to the TEE. Theencrypted private key may be decrypted within the TEE and used togenerate the digital signature for the transaction. The digitalsignature may then be fed back to the KMS 323. At step 1132, the useragent 411 may receive from the KMS a signed version of the blockchaintransaction.

At step 1134, the user agent 411 may send the DID document as well asthe signed blockchain transaction to the resolver 322 for sending to theblockchain system. At step 1136, the resolver 322 may send one or moretransactions to the blockchain system (e.g., one or more blockchainnodes, a BaaS Cloud 324). The transactions may invoke a blockchaincontract 331 for managing DIDs and DID documents on the blockchain 330.At step 1138, the resolver 322 may obtain information from theblockchain 330 indicating that the DID document has been successfullystored. At step 1140, the resolver 322 may forward a confirmation touser agent 411.

At step 1142, after a DID and its corresponding DID document have beencreated, the user agent 411 may update the database 416 to store amapping relationship among the DID, an account identifier of the user, aproof of identity authentication of the user, a service ID of the user,a public key associated with the DID, a key alias associated with theuser or the proof of identity authentication, other suitableinformation, or any combination thereof. In some embodiments, themapping relationship may be stored in an encrypted form. To store themapping relationship, the user agent 411 may calculate a hash value fora combination the DID and one or more items of the other identificationinformation. In some embodiments, such a hash value may be stored aspart of the DID document. The stored mapping relationship may allow theuser agent 441 to identify the DID based on information received fromthe user-side system 310. In some embodiments, the user agent 411 mayreceive a request associated with the obtained DID, wherein the requestcomprises the account identifier and then identify the obtained DIDbased on the mapping relationship between the account identifier and theobtained DID. In other embodiments, the user agent 441 may receive arequest for a proof of identity authentication, wherein the requestcomprises a DID and then locate the proof of identity authenticationbased on the mapping relationship between the proof of identityauthentication and the DID. In some embodiments, the user agent 411 maystore a recovery key for recovering the private key corresponding to theDID in association with identification information of the user. In thismanner, the user agent 411 may allow the user to take control over theDID using the recovery key. Then, at step 1144, the user agent 411 maysend information associated with the DID to the server 311, which maysend a notification to the user at step 1146 to inform the user of thesuccessful creation of the DID.

FIG. 12 illustrates a method for authenticating a decentralizedidentifier using an agent service in accordance with some embodiments.The operations of the method presented below are intended to beillustrative. Depending on the implementation, the method may includeadditional, fewer, or alternative steps performed in various orders orin parallel. In some embodiments, a party (e.g., verifier) may desire toauthenticate that another party (e.g., purported owner of DID) is thetrue owner of a DID. The authentication process may be facilitated byagent services 321 available to both parties.

In some embodiments, at step 1202, the verifier 532 may obtain a DIDprovided by a purported owner. At step 1204, the verifier 532 may send arequest to an agent service API 410 for creating a DID authenticationchallenge. The request may comprise the DID to be authenticated and anetwork address (e.g., a URL) to which a response to the challenge is tobe sent. The network address may be accessible to the verifier 532. Atstep 1206, the request may be forwarded from the agent service API 410to a verifier agent 413 configured to perform operations related toauthentication of DIDs. At step 1208, the verifier agent 413 may send aquery to a resolver 322 for the DID document associated with the DID tobe authenticated. At step 1210, the resolver 322 may formulate atransaction invoking a blockchain contract 331 for managing DIDs andsend the transaction to one or more blockchain nodes associated with theblockchain 330 for execution. As a result, the resolver 322 may obtainthe DID document corresponding to the DID at step 1212 and forward it tothe verifier agent 413 at step 1214. At step 1216, the verifier agent413 may create a DID authentication challenge based on the obtained DIDdocument. In some embodiments, the DID authentication challenge maycomprise a ciphertext created by encrypting original text using a publickey associated with the DID that is recorded in the DID document. Thechallenge may also comprise the network address associated with theverifier, to which a response is to be sent. At step 1218, the verifieragent 413 may obtain information associated with the authenticationservice endpoint for the DID from the DID document. At step 1220, theverifier agent 413 may store an identifier of the challenge in relationto information associated with the challenge in a memory using akey-value structure. For example, the verifier agent 413 may store achallenge ID associated with the challenge in association with the DIDto be authenticated, a plaintext used to create the cyphertext, and thenetwork address for sending the response to the challenge. At step 1222,the verifier agent 413 may send the challenge to the DID authenticationservices associated with the DID based on information from the DIDdocument.

In some embodiments, after obtaining the DID authentication challengefrom the verifier agent 413, the DID authentication services may obtainconsent from the owner of the DID for responding to such a challenge atstep 1224. If the owner provides consent or permission for the identityauthentication, the DID authentication services may send a request to anagent service API 410 associated with a user agent 411 for a response tothe DID authentication challenge at step 1226. At step 1228, the agentservice API 410 may call a corresponding functionality of the user agent411 for creation of a response to the challenge. The response to thechallenge may require restoration of the plaintext used to create theciphertext included in the challenge using a private key associated withthe DID to be authenticated. At step 1230, the user agent 411 may sendthe cyphertext from the challenge to the KMS 323 for decryption alongwith identification information associated with the DID that isrecognized by the KMS 323. The KMS 323 may store a plurality ofpublic-private key pairs in association with identification informationfor accounts or DIDs corresponding to the key pairs. Based on theidentification information received from the user agent 411, the KMS 323may identify the public-private key pair associated with the DID. Insome embodiments, the KMS 323 may store the public key and an encryptedversion of the private key. It may send the encrypted private key to aTEE associated with the KMS 323 for decryption. The private key may thenbe used to decrypt the ciphertext within the TEE. At step 1232, the useragent 411 may obtain the decrypted plaintext from the KMS 323.

At step 1234, the user agent 411 may generate a response to thechallenge using the plaintext and send the response back to the DIDauthentication services. The response may comprise a challengeidentifier that was contained in the original challenge. At step 1236,the DID authentication services may send the response to the networkaddress provided by the verifier 532. Then, at step 1238, the verifier532 may forward the response to the verifier agent 413 for checking. Theverifier agent 413 may first compare the challenge identifier in theresponse with one or more challenge identifiers stored in the memory 415to identify information associated with the challenge corresponding tothe response at step 1240. Then at step 1242, the verifier agent 413 maydetermine if the purported owner of the DID is the actual owner. In someembodiments, the verifier agent may determine if the plaintext containedin the response is identical to the plaintext used to create theciphertext in the challenge. If so, the verifier agent 413 may determinethat authentication is success. The verifier agent 413 may send aconfirmation message to the verifier at step 1244, which may forward theconfirmation message to the owner of the DID at step 1246.

FIG. 13 illustrates a method for issuing a verifiable claim using anagent service in accordance with some embodiments. The operations of themethod presented below are intended to be illustrative. Depending on theimplementation, the method may include additional, fewer, or alternativesteps performed in various orders or in parallel. In some embodiments, afirst entity (e.g., an issuer) may desire to issue a VC for a secondentity (e.g., a user) to testify as to a fact related to the secondentity. The process of issuing the VC may be facilitated by agentservices 321 available to the entities.

In some embodiments, an agent service API 410 may receive, from theissuer 531, a request for creating an unsigned VC for a DID associatedwith the user at step 1302. At step 1304, the agent service API 410 maycall the issuer agent 412 to execute operations to generate a new VC. Atstep 1306, the issuer agent 412 may create a VC based on the requestreceived from the issuer 531. The VC may comprise a message that isincluded in the request. In some embodiments, the VC may comprise anencrypted version of the message for confidentiality reasons. Themessage may comprise a claim or statement regarding the user or othersuitable information or data that may be conveyed to a party with accessto the VC. In some embodiments, the VC may comprise a claimcorresponding to identity authentication of the user (e.g., real-nameauthentication, real-person authentication). The request may comprise aDID of the user. The issuer agent 412 may directly create the VC basedon the DID. Alternatively, the request may comprise an accountidentifier associated with the user (e.g., the user's account with theentity issuing the VC). In this case, the issuer agent 412 may obtain anaccount identifier associated with the user from the request andidentify a DID based on a pre-stored mapping relationship between theaccount identifier and the DID. The issuer agent 412 may then create theunsigned VC based on the identified DID. The issuer agent 412 may alsocalculate a hash value of the content of the unsigned VC.

In some embodiments, the issuer agent 412 may obtain, in response toreceiving the request, a digital signature associated with the issuer.In some embodiments, the digital signature may be obtained from the KMS323. The issuer agent 412 may determine a key alias associated with theissuer 531 at step 1308. At step 1310, the issuer agent 412 may send arequest to the KMS 323 for a digital signature associated with theissuer 531 on the VC. The request may comprise the key alias, which maybe used for identification of the cryptographic keys associated with theissuer 531. The request may also comprise the hash value of the unsignedVC created by the issuer agent 412. The KMS 323 may store a plurality ofpublic-private key pairs in association with key aliases for entities orusers. Based on the key alias received from the issuer agent 412, theKMS 323 may identify the public-private key pair associated with theissuer 531. In some embodiments, the KMS 323 may store the public keyand an encrypted version of the private key. It may send the encryptedprivate key to a TEE associated with the KMS 323 for decryption. Theprivate key may then be used to create a digital signature of the issueron the VC. The digital signature may be created by encrypting the hashvalue of the unsigned VC using the private key. At step 1312, thedigital signature may be sent back to the issuer agent 412. Then, theissuer agent 412 may combine the unsigned VC with the digital signatureto compose a signed VC at step 1314. In this manner, the signed VC isgenerated based on the request received from the issuer 531 and thedigital signature.

In some embodiments, the issuer agent 412 may upload the VC to a serviceendpoint associated with the DID of the user or the holder of the VC.The issuer agent 412 may identify the service endpoint based on the DIDdocument associated with the DID. At step 1316, the issuer agent 412 maysend a query to a resolver 322 for the DID document associated with theDID for which the VC is issued. At step 1318, the resolver 322 mayformulate a transaction invoking a blockchain contract 331 for managingDIDs and send the transaction to one or more blockchain nodes associatedwith the blockchain 330 for execution. The transaction may compriseinformation associated with the DID and may be for retrieving a DIDdocument corresponding to the DID. As a result, the resolver 322 mayobtain the DID document corresponding to the DID at step 1320 andforward it to the SDK 312 at step 1322. Based on the DID document, theissuer agent 412 may obtain information (e.g., a network address)associated with a service endpoint (e.g., a VC repository 414) for theDID from the DID document. At step 1324, the issuer agent 412 may uploadthe VC to the service endpoint.

In some embodiments, the issuer agent 412 may store a status of the VC.The status of the VC may be stored in a blockchain 330. In someembodiments, the blockchain 330 may be used by a service endpointassociated with the issuer 531 of the VC. At step 1326, the issuer agent412 may send a status (e.g., valid, invalid) of the VC and a hash valueof the VC to the resolver 322 for storing in the blockchain 330. At step1328, the resolver 322 may generate and send to a blockchain node of theblockchain 330 associated with the service endpoint, a blockchaintransaction for adding information associated with the VC to theblockchain. The information may comprise the status and the hash valueof the VC. In some embodiments, the blockchain transaction may invoke ablockchain contract 331 for managing VCs. After sending the transactionto the blockchain node, the resolver 322 may determine that the hashvalue and status of the VC have been successfully stored at step 1330and may send a confirmation to the issuer agent 412 at step 1332. Insome embodiments, the status of the VC may also be stored locally. Atstep 1334, the issuer agent 412 may store the VC and its status at adatabase 416. The issuer agent 412 may receive a confirmation ofsuccessful storage at step 1336, send a confirmation to the agentservice API 410 at step 1338, which may then send a confirmation to theissuer 531 indicating that the VC has been successfully created at step1340. The confirmation to the issue may comprise the VC that has beencreated.

In some embodiments, the VC may be provided to the user or the holder ofthe VC. At step 1342, the issuer agent 412 may send the VC and/or astatus of the VC to an agent service API 410 associated with a useragent 411 for the holder of the VC. The agent service API 410 may callthe user agent 411 to upload the VC at step 1344. Here, the user agent411 may serve as a service endpoint for the DID of the holder of the VC.The user agent 411 may be implemented on the same physical system as theissuer agent 412. The user agent 411 may save the VC to a database 416at step 1346. After successful saving of the VC, the database 416 mayreturn a success confirmation to the user agent 411 at step 1348. Theuser agent 411 may send a confirmation to the agent service API 410 atstep 1350, which may forward a confirmation to the issuer agent 412 atstep 1352.

FIG. 14 illustrates a method for verifying a verifiable claim using anagent service in accordance with some embodiments. The operations of themethod presented below are intended to be illustrative. Depending on theimplementation, the method may include additional, fewer, or alternativesteps performed in various orders or in parallel. In some embodiments, aholder of a VC (or a subject of the VC) may present to a first entity(e.g., verifier) a VC issued by a second entity (e.g., issuer of theVC). The verifier may verify the VC with the aid of agent services 321.

In some embodiments, an agent service API 410 may receive from averifier 532 a request to verify a VC at step 1402. The VC may comprisea digital signature associated with an issuer of the VC. At step 1404,the agent service API 410 may call a function of the verifier agent 413for verifying the VC. In some embodiments, the verifier 532 may havedirectly obtained the VC from the holder of the VC. Alternatively, theverifier 532 may only have received an account identifier associatedwith a subject of the VC. The verifier 532 may obtain the VC byobtaining a DID associated with the subject of the VC based on apre-stored mapping relationship between the account identifier and theDID, obtaining a DID document associated with the DID, obtaininginformation associated with a service endpoint for managing VCs from theDID document, and obtaining the VC from the service endpoint.

In some embodiments, the verifier agent 413 may verify a status of theVC. The verifier agent 413 may obtain and verify the status using eithersteps 1406 a, 1408 a, 1410 a, and 1412 a or steps 1406 b, 1408 b, 1410b, and 1412 b. In some embodiments, the verifier agent 413 may obtainthe status of the VC from a blockchain storing information associatedwith a plurality of VCs. At step 1406 a, the verifier agent 413 may sendto a resolver 322 a query for a status of the VC. The query may comprisean identifier of the VC. At step 1408 a, the resolver 322 may create ablockchain transaction for retrieving a hash value and a status of theVC and send it to one or more blockchain nodes associated with ablockchain 300. The blockchain transaction may comprise a DID of thesubject of the VC and may invoke a blockchain contract 331 for managingVCs. At step 1410 a, the resolver 322 may obtain a status of the VC aswell as a hash value associated with the VC from the blockchain 330. Theresolver 322 may then send the hash value and status to the verifieragent 413 at step 1412 a for verification. The verifier agent 413 maycalculate a hash value by applying a hash function on the VC that wasprovided by the holder. The verifier agent 413 may authenticate thereceived status of the VC by comparing the hash value received from theblockchain 330 with the calculated hash value. If they are identical,the verifier agent 413 may determine that the received status doescorrespond to the VC. If the status indicates that the VC is valid, theverifier agent 413 may complete this step of the verification.

In some embodiments, the verifier agent 413 may obtain the status of theVC from a service endpoint associated with the VC. In some embodiments,the service endpoint may correspond to an issuer agent 412 associatedwith the issuer. At step 1406 b, the verifier agent 413 may send a queryto the issuer agent 412 for status of the VC. The issuer agent 412 mayquery the database 416 for the status of the VC at step 1408 b andobtain a status and a corresponding hash value of the VC at step 1410 b.The issuer agent 412 may send the hash value and the status to theverifier agent 413 at step 1412 b. The verifier agent 413 mayauthenticate the status and verify that the VC is valid in the mannerdiscussed above.

In some embodiments, the verifier agent 413 may determine that the VC isissued by the issuer identified on the VC. The verifier agent 413 mayobtain, based on the VC, a public key associated with the issuer. Theverifier agent 413 may identify the issuer based on an identifier in theVC. In some embodiments, the identifier may comprise a DID of theissuer. The public key may be obtained from the blockchain 330 based onthe DID of the issuer. At step 1414, the verifier agent 413 may send arequest to the resolver 322 for the public key associated with theissuer. The request may comprise the DID of the issuer. At step 1416,the resolver 322 may create a blockchain transaction invoking ablockchain contract 331 for retrieving a public key or a DID documentbased on a DID and send the blockchain transaction to a blockchain nodeof the blockchain 330. The resolver 322 may obtain the public key (e.g.,by retrieving from the DID document) at step 1418 and forward the publickey to the verifier agent 413 at step 1420. Then, at step 1422, theverifier agent 413 may verify the VC using the public key by determiningthat the digital signature is created based on a private key associatedwith the public key. In some embodiments, the verifier agent 413 mayverify one or more other facts about the VC. For example, the verifieragent 413 may obtain, from the VC, an issuance date of the VC andvalidate the obtained issuance date based on a comparison between theobtained issuance date and a current date. As another example, theverifier agent 413 may obtain, from the VC, an expiration date of the VCand validate that the VC has not expired based on the expiration dateand a current date. If verification of the VC is successful, theverifier agent may send a confirmation to the agent service API 410 atstep 1424. The agent service API 410 may send a message to the verifier532 confirming that the VC is verified at step 1426.

FIG. 15 illustrates a flowchart of a method for creating a decentralizedidentifier in accordance with some embodiments. The method 1500 may beperformed by a device, apparatus, or system for DID creation. The method1500 may be performed by one or more components of the environment orsystem illustrated by FIGS. 1-5, such as one or more components of theagent services 321, one or more components of the resolver services 322,or one or more components of the BaaS cloud 324. Depending on theimplementation, the method 1500 may include additional, fewer, oralternative steps performed in various orders or in parallel.

Block 1510 includes receiving a request for obtaining a decentralizedidentifier (DID), wherein the request comprises an account identifier.In some embodiments, receiving a request for obtaining a DID comprisesreceiving the request from a first entity on behalf of a second entityfor creating the DID for the second entity, wherein the accountidentifier corresponds to the second entity. In some embodiments, themethod further comprises determining an existing DID associated with thefirst entity based on the request. In some embodiments, the methodfurther comprises determining that the request comprises a proof ofreal-name authentication of the second entity. In some embodiments, therequest comprises an application programming interface (API) message.

Block 1520 includes obtaining, in response to receiving the request, apublic key of a cryptographic key pair. In some embodiments, theobtaining a public key of a cryptographic key pair comprises sending arequest to a key management system (KMS) for generating and storing thecryptographic key pair and receiving the public key of the cryptographickey pair from the KMS.

Block 1530 includes obtaining the DID based on the public key. In someembodiments, the obtaining a DID comprises generating a blockchaintransaction for creating a blockchain account, wherein the obtained DIDcomprises a blockchain address associated with the blockchain account.In some embodiments, the obtaining a DID comprises generating, based onthe public key, one or more blockchain transactions for creating the DIDand adding a DID document associated with the DID to a blockchain. Insome embodiments, the one or more blockchain transactions invoke one ormore blockchain contracts associated with the blockchain. In someembodiments, the obtaining a DID comprises sending a request to a KMSfor signing a blockchain transaction using a private key of thecryptographic key pair and receiving from the KMS a signed version ofthe blockchain transaction, wherein the signed version of the blockchaintransaction is generated in a Trusted Execution Environment (TEE).

In some embodiments, the DID document comprises one or more public keysassociated with the obtained DID, authentication information associatedwith the obtained DID, authorization information associated with theobtained DID, delegation information associated with the obtained DID,one or more services associated with the obtained DID, one or moreservice endpoints associated with the obtained DID, or a DID of acreator of the obtained DID. In some embodiments, the DID documentcomprises the mapping relationship between the account identifier andthe obtained DID. In some embodiments, the mapping relationship in theDID document is encrypted.

Block 1540 includes storing a mapping relationship between the accountidentifier and the obtained DID. In some embodiments, the method furthercomprises receiving a request associated with the obtained DID, whereinthe request comprises the account identifier and identifying theobtained DID based on the mapping relationship between the accountidentifier and the obtained DID. In some embodiments, the method furthercomprises storing a recovery key associated with the obtained DID.

FIG. 16 illustrates a flowchart of a method for issuing a verifiableclaim in accordance with some embodiments. The method 1600 may beperformed by a device, apparatus, or system for VC issuance. The method1600 may be performed by one or more components of the environment orsystem illustrated by FIGS. 1-5, such as one or more components of theagent services 321, one or more components of the resolver services 322,or one or more components of the BaaS cloud 324. Depending on theimplementation, the method 1600 may include additional, fewer, oralternative steps performed in various orders or in parallel.

Block 1610 includes receiving, from a first entity, a request forcreating a verifiable claim (VC) for a decentralized identifier (DID)associated with a second entity. In some embodiments, the receiving arequest for creating a VC for a DID associated with a second entitycomprises obtaining an account identifier associated with a secondentity from the request and identifying the DID based on a pre-storedmapping relationship between the account identifier and the DID.

Block 1620 includes obtaining, in response to receiving the request, adigital signature associated with the first entity. In some embodiments,the obtaining a digital signature associated with the first entitycomprises determining, based on the received request, a key aliasassociated with the first entity, sending a request to a key managementsystem (KMS) for the digital signature associated with the first entity,the request comprising the key alias, and receiving the digitalsignature from the KMS. In some embodiments, the obtaining a digitalsignature associated with the first entity comprises obtaining a messagefrom the received request, creating an un-signed VC based at least inpart on the message, determining a hash value of the un-signed VC,sending a request to a key management system (KMS) for the digitalsignature, the request comprising the hash value, and receiving thedigital signature from the KMS.

Block 1630 includes generating the VC based on the received request andthe obtained digital signature. In some embodiments, the generating theVC comprises generating the VC based on an encrypted message included inthe received request. In some embodiments, the generated VC comprises aclaim corresponding to real-name authentication of the second entity.

In some embodiments, the method further comprises uploading the VC to aservice endpoint associated with the DID. In some embodiments, theuploading the VC to a service endpoint associated with the DID comprisessending a blockchain transaction to a blockchain node for adding to ablockchain, wherein the blockchain transaction comprises informationassociated with the DID and is for retrieving a DID documentcorresponding to the DID, obtaining the DID document from theblockchain, and determining the service endpoint associated with the DIDbased on the DID document. In some embodiments, the service endpoint isassociated with a blockchain. In some embodiments, the uploading the VCto the service endpoint comprises sending, to a blockchain node of theblockchain associated with the service endpoint, a blockchaintransaction for adding information associated with the VC to theblockchain associated with the service endpoint. In some embodiments,the blockchain transaction invokes a blockchain contract for managingVCs.

In some embodiments, the method further comprises storing the generatedVC and a status associated with the generated VC. In some embodiments,the method further comprises sending the generated VC and a statusassociated with the generated VC to an online agent accessible to thesecond entity via an application programming interface (API) forstoring. In some embodiments, the method further comprises sending asuccess message to the first entity, the success message comprising thegenerated VC.

FIG. 17 illustrates a flowchart of a method for verifying a verifiableclaim in accordance with some embodiments. The method 1700 may beperformed by a device, apparatus, or system for VC verification. Themethod 1700 may be performed by one or more components of theenvironment or system illustrated by FIGS. 1-5, such as one or morecomponents of the agent services 321, one or more components of theresolver services 322, or one or more components of the BaaS cloud 324.Depending on the implementation, the method 1700 may include additional,fewer, or alternative steps performed in various orders or in parallel.

Block 1710 includes receiving, from a first entity, a request forverifying a verifiable claim (VC) that comprises a digital signature.Block 1720 includes obtaining, based on the VC, a public key associatedwith a second entity. In some embodiments, the obtaining a public keyassociated with a second entity comprises identifying the second entitybased on an identifier in the VC. In some embodiments, the identifier inthe VC is a decentralized identifier (DID); the obtaining a public keyassociated with a second entity comprises sending, to a blockchain nodeof a blockchain, a blockchain transaction comprising informationassociated with the DID, wherein the blockchain transaction is forretrieving a DID document corresponding to the DID, obtaining the DIDdocument from the blockchain, and retrieving a public key from the DIDdocument. In some embodiments, the blockchain transaction invokes ablockchain contract for managing relationships between DIDs and DIDdocuments.

Block 1730 includes determining that the digital signature is createdbased on a private key associated with the public key. Block 1740includes verifying the VC based on the determination. In someembodiments, the verifying the VC comprises obtaining, from the VC, anissuance date of the VC and validating the obtained issuance date basedon a comparison between the obtained issuance date and a current date.In some embodiments, the verifying the VC comprises obtaining, from theVC, an expiration date of the VC and validating that the VC has notexpired based on the expiration date and a current date.

In some embodiments, the method further comprises obtaining a status ofthe VC and determining that the status of the VC is valid. In someembodiments, the obtaining a status of the VC comprises obtaining thestatus from a blockchain storing information associated with a pluralityof VCs. In some embodiments, the determining that the status of the VCis valid comprises obtaining a first hash value associated with the VCalong with the status of the VC, determining a second hash value byapplying a hash function on the VC, and authenticating the status of theVC by comparing the first hash value with the second hash value. In someembodiments, the obtaining a first hash value associated with the VCalong with the status of the VC comprises sending, to a blockchain nodeof the blockchain, a blockchain transaction for retrieving the firsthash value and the status, the blockchain transaction comprising the DIDassociated with the subject of the VC.

In some embodiments, the method further comprises receiving, from thefirst entity, an account identifier associated with a subject of the VC,obtaining a DID associated with the subject of the VC based on apre-stored mapping relationship between the account identifier and theDID, obtaining a DID document associated with the DID, obtaininginformation associated with a service endpoint for managing VCs from theDID document, and obtaining the VC from the service endpoint. In someembodiments, the method further comprises sending a message to the firstentity confirming that the VC is verified.

FIG. 18 illustrates a block diagram of a computer system for creating adecentralized identifier in accordance with some embodiments. The system1800 may be an example of an implementation of one or more components ofthe service-side system 320 of FIG. 3 or one or more other componentsillustrated in FIGS. 1-5. The method 1500 may be implemented by thecomputer system 1800. The computer system 1800 may comprise one or moreprocessors and one or more non-transitory computer-readable storagemedia (e.g., one or more memories) coupled to the one or more processorsand configured with instructions executable by the one or moreprocessors to cause the system or device (e.g., the processor) toperform the above-described method, e.g., the method 1500. The computersystem 1800 may comprise various units/modules corresponding to theinstructions (e.g., software instructions). In some embodiments, thecomputer system 1800 may be referred to as an apparatus for creating aDID. The apparatus may comprise a receiving module 1810 for receiving arequest for obtaining a decentralized identifier (DID), wherein therequest comprises an account identifier; a first obtaining module 1820for obtaining, in response to receiving the request, a public key of acryptographic key pair; a second obtaining module 1830 for obtaining theDID based on the public key; and a storing module 1840 for storing amapping relationship between the account identifier and the obtainedDID.

FIG. 19 illustrates a block diagram of a computer system for issuing averifiable claim in accordance with some embodiments. The system 1900may be an example of an implementation of one or more components of theservice-side system 320 of FIG. 3 or one or more other componentsillustrated in FIGS. 1-5. The method 1600 may be implemented by thecomputer system 1900. The computer system 1900 may comprise one or moreprocessors and one or more non-transitory computer-readable storagemedia (e.g., one or more memories) coupled to the one or more processorsand configured with instructions executable by the one or moreprocessors to cause the system or device (e.g., the processor) toperform the above-described method, e.g., the method 1600. The computersystem 1900 may comprise various units/modules corresponding to theinstructions (e.g., software instructions). In some embodiments, thecomputer system 1900 may be referred to as an apparatus for issuing aVC. The apparatus may comprise a receiving module 1910 for receiving,from a first entity, a request for creating a verifiable claim (VC) fora decentralized identifier (DID) associated with a second entity; anobtaining module 1920 for obtaining, in response to receiving therequest, a digital signature associated with the first entity; and agenerating module 1930 for generating the VC based on the receivedrequest and the obtained digital signature.

FIG. 20 illustrates a block diagram of a computer system for verifying averifiable claim in accordance with some embodiments. The system 2000may be an example of an implementation of one or more components of theservice-side system 320 of FIG. 3 or one or more other componentsillustrated in FIGS. 1-5. The method 1700 may be implemented by thecomputer system 2000. The computer system 2000 may comprise one or moreprocessors and one or more non-transitory computer-readable storagemedia (e.g., one or more memories) coupled to the one or more processorsand configured with instructions executable by the one or moreprocessors to cause the system or device (e.g., the processor) toperform the above-described method, e.g., the method 1700. The computersystem 2000 may comprise various units/modules corresponding to theinstructions (e.g., software instructions). In some embodiments, thecomputer system 2000 may be referred to as an apparatus for verifying aVC. The apparatus may comprise a receiving module 2010 for receiving,from a first entity, a request for verifying a verifiable claim (VC)that comprises a digital signature; an obtaining module 2020 forobtaining, based on the VC, a public key associated with a secondentity; a determining module 2030 for determining that the digitalsignature is created based on a private key associated with the publickey; and a verifying module 2040 for verifying the VC based on thedetermination.

The techniques described herein are implemented by one or morespecial-purpose computing devices. The special-purpose computing devicesmay be desktop computer systems, server computer systems, portablecomputer systems, handheld devices, networking devices or any otherdevice or combination of devices that incorporate hard-wired and/orprogram logic to implement the techniques. The special-purpose computingdevices may be implemented as personal computers, laptops, cellularphones, camera phones, smart phones, personal digital assistants, mediaplayers, navigation devices, email devices, game consoles, tabletcomputers, wearable devices, or a combination thereof. Computingdevice(s) are generally controlled and coordinated by operating systemsoftware. Conventional operating systems control and schedule computerprocesses for execution, perform memory management, provide file system,networking, I/O services, and provide a user interface functionality,such as a graphical user interface (“GUI”), among other things. Thevarious systems, apparatuses, storage media, modules, and unitsdescribed herein may be implemented in the special-purpose computingdevices, or one or more computing chips of the one or morespecial-purpose computing devices. In some embodiments, the instructionsdescribed herein may be implemented in a virtual machine on thespecial-purpose computing device. When executed, the instructions maycause the special-purpose computing device to perform various methodsdescribed herein. The virtual machine may include a software, hardware,or a combination thereof.

FIG. 21 illustrates a block diagram of a computer system in which any ofthe embodiments described herein may be implemented. The system 2100 maybe implemented in any of the components of the environments or systemsillustrated in FIGS. 1-5. the software applications or servicesillustrated in FIGS. 1-5 may be implemented and operated on the system2100. One or more of the example methods illustrated by FIGS. 6-17 maybe performed by one or more implementations of the computer system 2100.

The computer system 2100 may include a bus 2102 or other communicationmechanism for communicating information, one or more hardwareprocessor(s) 2104 coupled with bus 2102 for processing information.Hardware processor(s) 2104 may be, for example, one or more generalpurpose microprocessors.

The computer system 2100 may also include a main memory 2106, such as arandom access memory (RAM), cache and/or other dynamic storage devices,coupled to bus 2102 for storing information and instructions executableby processor(s) 2104. Main memory 2106 also may be used for storingtemporary variables or other intermediate information during executionof instructions executable by processor(s) 2104. Such instructions, whenstored in storage media accessible to processor(s) 2104, render computersystem 2100 into a special-purpose machine that is customized to performthe operations specified in the instructions. The computer system 2100may further include a read only memory (ROM) 2108 or other staticstorage device coupled to bus 2102 for storing static information andinstructions for processor(s) 2104. A storage device 2110, such as amagnetic disk, optical disk, or USB thumb drive (Flash drive), etc., maybe provided and coupled to bus 2102 for storing information andinstructions.

The computer system 2100 may implement the techniques described hereinusing customized hard-wired logic, one or more ASICs or FPGAs, firmwareand/or program logic which in combination with the computer systemcauses or programs computer system 2100 to be a special-purpose machine.According to one embodiment, the operations, methods, and processesdescribed herein are performed by computer system 2100 in response toprocessor(s) 2104 executing one or more sequences of one or moreinstructions contained in main memory 2106. Such instructions may beread into main memory 2106 from another storage medium, such as storagedevice 2110. Execution of the sequences of instructions contained inmain memory 2106 may cause processor(s) 2104 to perform the processsteps described herein. In alternative embodiments, hard-wired circuitrymay be used in place of or in combination with software instructions.

The main memory 2106, the ROM 2108, and/or the storage device 2110 mayinclude non-transitory storage media. The term “non-transitory media,”and similar terms, as used herein refers to media that store data and/orinstructions that cause a machine to operate in a specific fashion, themedia excludes transitory signals. Such non-transitory media maycomprise non-volatile media and/or volatile media. Non-volatile mediaincludes, for example, optical or magnetic disks, such as storage device2110. Volatile media includes dynamic memory, such as main memory 2106.Common forms of non-transitory media include, for example, a floppydisk, a flexible disk, hard disk, solid state drive, magnetic tape, orany other magnetic data storage medium, a CD-ROM, any other optical datastorage medium, any physical medium with patterns of holes, a RAM, aPROM, and EPROM, a FLASH-EPROM, NVRAM, any other memory chip orcartridge, and networked versions of the same.

The computer system 2100 may include a network interface 2118 coupled tobus 2102. Network interface 2118 may provide a two-way datacommunication coupling to one or more network links that are connectedto one or more local networks. For example, network interface 2118 maybe an integrated services digital network (ISDN) card, cable modem,satellite modem, or a modem to provide a data communication connectionto a corresponding type of telephone line. As another example, networkinterface 2118 may be a local area network (LAN) card to provide a datacommunication connection to a compatible LAN (or WAN component tocommunicate with a WAN). Wireless links may also be implemented. In anysuch implementation, network interface 2118 may send and receiveelectrical, electromagnetic or optical signals that carry digital datastreams representing various types of information.

The computer system 2100 can send messages and receive data, includingprogram code, through the network(s), network link and network interface2118. In the Internet example, a server might transmit a requested codefor an application program through the Internet, the ISP, the localnetwork and the network interface 2118.

The received code may be executed by processor(s) 2104 as it isreceived, and/or stored in storage device 2110, or other non-volatilestorage for later execution.

Each of the processes, methods, and algorithms described in thepreceding sections may be embodied in, and fully or partially automatedby, code modules executed by one or more computer systems or computerprocessors comprising computer hardware. The processes and algorithmsmay be implemented partially or wholly in application-specificcircuitry.

The various features and processes described above may be usedindependently of one another or may be combined in various ways. Allpossible combinations and sub-combinations are intended to fall withinthe scope of this specification. In addition, certain method or processblocks may be omitted in some implementations. The methods and processesdescribed herein are also not limited to any particular sequence, andthe blocks or states relating thereto can be performed in othersequences that are appropriate. For example, described blocks or statesmay be performed in an order other than that specifically disclosed, ormultiple blocks or states may be combined in a single block or state.The examples of blocks or states may be performed in serial, inparallel, or in some other manner. Blocks or states may be added to orremoved from the disclosed embodiments. The examples of systems andcomponents described herein may be configured differently thandescribed. For example, elements may be added to, removed from, orrearranged compared to the disclosed embodiments.

The various operations of methods described herein may be performed, atleast partially, by one or more processors that are temporarilyconfigured (e.g., by software) or permanently configured to perform therelevant operations. Whether temporarily or permanently configured, suchprocessors may constitute processor-implemented engines that operate toperform one or more operations or functions described herein.

Similarly, the methods described herein may be at least partiallyprocessor-implemented, with a particular processor or processors beingan example of hardware. For example, at least some of the operations ofa method may be performed by one or more processors orprocessor-implemented engines. Moreover, the one or more processors mayalso operate to support performance of the relevant operations in a“cloud computing” environment or as a “software as a service” (SaaS).For example, at least some of the operations may be performed by a groupof computers (as examples of machines including processors), with theseoperations being accessible via a network (e.g., the Internet) and viaone or more appropriate interfaces (e.g., an Application ProgramInterface (API)).

The performance of certain of the operations may be distributed amongthe processors, not only residing within a single machine, but deployedacross a number of machines. In some embodiments, the processors orprocessor-implemented engines may be located in a single geographiclocation (e.g., within a home environment, an office environment, or aserver farm). In other embodiments, the processors orprocessor-implemented engines may be distributed across a number ofgeographic locations.

Throughout this specification, plural instances may implementcomponents, operations, or structures described as a single instance.Although individual operations of one or more methods are illustratedand described as separate operations, one or more of the individualoperations may be performed concurrently, and nothing requires that theoperations be performed in the order illustrated. Structures andfunctionality presented as separate components in configurations may beimplemented as a combined structure or component. Similarly, structuresand functionality presented as a single component may be implemented asseparate components. These and other variations, modifications,additions, and improvements fall within the scope of the subject matterherein.

Although an overview of the subject matter has been described withreference to specific embodiments, various modifications and changes maybe made to these embodiments without departing from the broader scope ofembodiments of the specification. The Detailed Description should not tobe taken in a limiting sense, and the scope of various embodiments isdefined only by the appended claims, along with the full range ofequivalents to which such claims are entitled. Furthermore, relatedterms (such as “first,” “second,” “third,” etc.) used herein do notdenote any order, height, or importance, but rather are used todistinguish one element from another element. Furthermore, the terms“a,” “an,” and “plurality” do not denote a limitation of quantityherein, but rather denote the presence of at least one of the articlesmentioned.

The invention claimed is:
 1. A computer-implemented method for claimverification, comprising: receiving, from a first entity, a request forverifying a verifiable claim (VC) that comprises a digital signature ofa second entity and a decentralized identifier (DID) of the secondentity, wherein the VC is generated based on a DID of a third entity;obtaining the DID associated with the second entity from the VC;sending, to a blockchain node of a blockchain, a first blockchaintransaction comprising information associated with the DID associatedwith the second entity, wherein the blockchain transaction is forretrieving a DID document corresponding to the DID associated with thesecond entity; obtaining a public key associated with the second entitybased on the DID document; determining that the digital signature iscreated based on a private key associated with the public key;generating a second blockchain transaction for retrieving a hash valueand a status of the VC from the blockchain, wherein the secondblockchain transaction comprises the DID associated with the thirdentity and invokes a blockchain contract for managing VCs, theblockchain contract comprising instructions executable by a plurality ofblockchain nodes of the blockchain; sending the second blockchaintransaction to a blockchain node of the blockchain for the blockchainnode to verify the second blockchain transaction, to execute the invokedblockchain contract, and to add the second blockchain transaction to theblockchain; obtaining, from the blockchain, the hash value and thestatus of the VC; authenticating the obtained status of the VC based onthe obtained hash value and a hash function associated with the thirdentity; and verifying the VC based on the determining that the digitalsignature is created based on the private key associated with the publickey, the authenticating the obtained status of the VC being successful,and that the status of the VC indicates that the VC is valid.
 2. Themethod of claim 1, wherein the first blockchain transaction invokes ablockchain contract for managing relationships between DIDs and DIDdocuments.
 3. The method of claim 1, wherein the authenticating theobtained status of the VC comprises: determining a hash value byapplying the hash function on the VC; and authenticating the status ofthe VC by comparing the hash value obtained from the blockchain with thehash value determined by applying the hash function.
 4. The method ofclaim 1, further comprising: receiving, from the first entity, anaccount identifier associated with the third entity; obtaining a DIDassociated with the third entity subject of the VC based on a pre-storedmapping relationship between the account identifier and the DIDassociated with the third entity; obtaining a DID document associatedwith the DID associated with the third entity; obtaining informationassociated with a service endpoint for managing VCs from the DIDdocument; and obtaining the VC from the service endpoint.
 5. The methodof claim 1, further comprising: sending a message to the first entityconfirming that the VC is verified.
 6. The method of claim 1, whereinthe verifying the VC comprises: obtaining, from the VC, an issuance dateof the VC; and validating the obtained issuance date based on acomparison between the obtained issuance date and a current date.
 7. Themethod of claim 1, wherein the verifying the VC comprises: obtaining,from the VC, an expiration date of the VC; and validating that the VChas not expired based on the expiration date and a current date.
 8. Anon-transitory computer-readable storage medium for claim verification,configured with instructions executable by one or more processors tocause the one or more processors to perform operations comprising:receiving, from a first entity, a request for verifying a verifiableclaim (VC) that comprises a digital signature of a second entity and adecentralized identifier (DID) of the second entity, wherein the VC isgenerated based on a DID of a third entity; obtaining the DID associatedwith the second entity from the VC; sending, to a blockchain node of ablockchain, a first blockchain transaction comprising informationassociated with the DID associated with the second entity, wherein theblockchain transaction is for retrieving a DID document corresponding tothe DID associated with the second entity; obtaining a public keyassociated with the second entity based on the DID document; determiningthat the digital signature is created based on a private key associatedwith the public key; generating a second blockchain transaction forretrieving a hash value and a status of the VC from the blockchain,wherein the second blockchain transaction comprises the DID associatedwith the third entity and invokes a blockchain contract for managingVCs, the blockchain contract comprising instructions executable by aplurality of blockchain nodes of the blockchain; sending the secondblockchain transaction to a blockchain node of the blockchain for theblockchain node to verify the second blockchain transaction, to executethe invoked blockchain contract, and to add the second blockchaintransaction to the blockchain; obtaining, from the blockchain, the hashvalue and the status of the VC; authenticating the obtained status ofthe VC based on the obtained hash value and a hash function associatedwith the third entity; and verifying the VC based on the determiningthat the digital signature is created based on the private keyassociated with the public key, the authenticating the obtained statusof the VC being successful, and that the status of the VC indicates thatthe VC is valid.
 9. The non-transitory computer-readable storage mediumof claim 8, wherein the first blockchain transaction invokes ablockchain contract for managing relationships between DIDs and DIDdocuments.
 10. The non-transitory computer-readable storage medium ofclaim 8, wherein the authenticating the obtained status of the VCcomprises: determining a hash value by applying the hash function on theVC; and authenticating the status of the VC by comparing the hash valueobtained from the blockchain with the hash value determined by applyingthe hash function.
 11. The non-transitory computer-readable storagemedium of claim 8, wherein the operations further comprise: receiving,from the first entity, an account identifier associated with the thirdentity; obtaining a DID associated with the third entity based on apre-stored mapping relationship between the account identifier and theDID associated with the third entity; obtaining a DID documentassociated with the DID associated with the third entity; obtaininginformation associated with a service endpoint for managing VCs from theDID document; and obtaining the VC from the service endpoint.
 12. Thenon-transitory computer-readable storage medium of claim 8, wherein theoperations further comprise: sending a message to the first entityconfirming that the VC is verified.
 13. The non-transitorycomputer-readable storage medium of claim 8, wherein the verifying theVC comprises: obtaining, from the VC, an issuance date of the VC; andvalidating the obtained issuance date based on a comparison between theobtained issuance date and a current date.
 14. A system for claimverification, comprising a processor and a non-transitorycomputer-readable storage medium storing instructions executable by theprocessor to cause the system to perform operations comprising:receiving, from a first entity, a request for verifying a verifiableclaim (VC) that comprises a digital signature of a second entity and adecentralized identifier (DID) of the second entity, wherein the VC isgenerated based on a DID of a third entity; obtaining the DID associatedwith the second entity from the VC; sending, to a blockchain node of ablockchain, a first blockchain transaction comprising informationassociated with the DID associated with the second entity, wherein theblockchain transaction is for retrieving a DID document corresponding tothe DID associated with the second entity; obtaining a public keyassociated with the second entity based on the DID document; determiningthat the digital signature is created based on a private key associatedwith the public key; generating a second blockchain transaction forretrieving a hash value and a status of the VC from the blockchain,wherein the second blockchain transaction comprises the DID associatedwith the third entity and invokes a blockchain contract for managingVCs, the blockchain contract comprising instructions executable by aplurality of blockchain nodes of the blockchain; sending the secondblockchain transaction to a blockchain node of the blockchain for theblockchain node to verify the second blockchain transaction, to executethe invoked blockchain contract, and to add the second blockchaintransaction to the blockchain; obtaining, from the blockchain, the hashvalue and the status of the VC; authenticating the obtained status ofthe VC based on the obtained hash value and a hash function associatedwith the third entity; and verifying the VC based on the determiningthat the digital signature is created based on the private keyassociated with the public key, the authenticating the obtained statusof the VC being successful, and that the status of the VC indicates thatthe VC is valid.